Splunk On-Call Pricing, Features, Reviews and Alternatives

- Communication-centric design - great for team efforts - Very responsive support and dev team - Easy to set up, easy to use - Lots of integrations available - Contact details in the app makes reaching out to teammates easier in a crisis

- Some advanced/niche scheduling options are not currently possible - Data on old alerts can be difficult or impossible to obtain, depending on age - Reporting is a work in progress

It's wonderful affirmation for us when we hear that VictorOps has been a positive driver in team efficiency and happiness! We're also continuing to advance our development efforts (our engineering team is also growing!), so keep an eye out for enhancements on reporting and scheduling!

VictorOps was easy to deploy, configure teams, and manage on-call rotations. There is a large list of integrations that allow for connections into all our required systems. Included with every integration is a link to their knowledge base. VictorOps is a must have tool for anyone looking to more effectively manage alert escalation and on-call rotations.

There are only two things i have come across that are lacking. First, setting up overrides for on call management. VictorOps only allows for overrides to be in 30 minutes time blocks. This has caused issues with emergency on call coverage. Second is no having a location, out side the alerts and incidents, to house knowledge base type documents.

VictorOps (now called Splunk On-Call) organizes incidents in a manner similar to a Twitter timeline. It's really convenient being able to browse your history like that. There are a decent number of integrations with third-party services, and the Rule Engine allows you to annotate incoming alerts with additional information such as links to runbooks. In terms of price, you'll pay a lot less than you will for competing products like PagerDuty.

Since being acquired by Splunk, VictorOps has been left to rot on the vine. There have been virtually no new features. I was willing to excuse that when VictorOps was operating as a smaller company, but not being able to do an in-depth history of incidents in 2021 is just inexcusable. Splunk's high-pressure sales agents will constantly try to upsell you on other Splunk products. SSO integration is still awkward to set up and use, and there still aren't nearly as many integrations as with PagerDuty.

Provides all of the necessary functionality for managing multiple teams of on-call professionals across an organization. App and Slack integration provide a feature-rich experience. override existing schedules, acknowledge or snooze alerts, see detailed history, and run reports.

Some features are buried in menus, and the calendar is a little hard to use at times. Some options require clicking a specific toggle icon instead of just the text.

The transmogrifier has been an extremely useful tool for many of our teams. We've added playbook annotations to most of our alerts which has been a boon for our 24 by 7 support team. The Datadog integration has also shown VictorOps's savviness and people-centric approach to building a product. A Datadog VictorOps incident will send all of the pertinent information and graphs to an on-call users phone....

Read more

VictorOps is still lacking some of PagerDuty's clerical and reporting functionality; for example, we no longer have the ability to easily reference a specific incident in the past.

Thanks for such a positive review! We see people make the switch from PagerDuty on a regular basis, not just because of our feature set, but because we also put our users first. It's great that you noticed that too. It's also good to note that if you capture each incident as a post-mortem report, you'll always be able to go back and reference it. However if you need a more specific way to reference past incidents, I would definitely suggest you drop our support team a line. They are constantly looking for ways to improve the product, and would love to hear your ideas.