Overall Satisfaction with VictorOps
We use VictorOps as alternative to something like PagerDuty, basically to alert the "engineer on-call" of any issues that may occur throughout our platform. We run a weekly engineering on-call rotation and have alerts set up to detect problems or potential issues and have someone to address them as soon as possible.
- Good text and call alerting.
- Allows setting up on-call schedules for months at a time.
- The UI is a little clunky.
- It's a little tricky to override or shift schedules (i.e., for a particular day in a one-week rotation).
- Saves money by being cost-effective alerting solution.
- It helps maintain platform uptime, giving customers the reliability they expect.
VictorOps support has proven excellent for us. Because it is such a widely used tool, there is a lot of documentation on usage, and a large community of users to lean on. Also, many engineers have had experience working with VictorOps already, and the tool is so easy to setup / manage that much support isn't really necessary.
Do you think Splunk On-Call delivers good value for the price?
Are you happy with Splunk On-Call's feature set?
Did Splunk On-Call live up to sales and marketing promises?
Did implementation of Splunk On-Call go as expected?
Would you buy Splunk On-Call again?
VictorOps is an excellent option for platform alerting and is very cost-effective. For teams of any size, it can be the correct tool. VictorOps success is mainly dependent on the amount of logging and monitoring setup within your platform. If you have little or poor logging, then they may not be anything for VictorOps to act upon.