PagerDuty, Inc. (NYSE:PD) provides digital operations management. Serving organizations of all sizes, PagerDuty aims to help them deliver a perfect digital experience to their customers, every time.
$25
per month per user
Splunk On-Call
Score 6.1 out of 10
N/A
Formerly known as VictorOps, Splunk On-Call is an incident response system for developers, devops and operations teams that helps reduce outage time.
I think PagerDuty is a good product. I have used VictorOps before and found the interface to be too cumbersome and tedious to set up. They have a rich interface with many great integrations, but sometimes less is more, and I have found this to be the case with Pager Duty. They …
VictorOps is similar to PagerDuty, but was much more difficult to setup and get working with the Nagios system I was supporting. I also did not like the mobile app for VictorOps, it was too convoluted and hard to figure out what alert was being sent to the on-call person. I …
VictorOps was ok. PagerDuty allowed more flexibility in scheduling from what I recall. I wasn't involved with the decision making but in our testing VictorOps wasn't as comfortable to use as PagerDuty.
When compared to VictorOps and OpsGenie, PagerDuty is clearly the best of the breed. It provides a more polished UI, more integrations, and more features than the others, but it's priced at a premium. Smaller teams will probably get more value out of another alternative that …
I worked at one company that used VictorOps (now Splunk On-Call) and it was quite similar to PagerDuty. VictorOps had a smaller customer base and fewer integrations, so there was less information on the Internet about how to use it effectively, and I don't think its API was as …
When we selected PagerDuty, we evaluated a few other solutions including Moogsoft, BigPanda, VictorOps and Splunk Enterprise. We decided on PagerDuty specifically for the automated on-call escalation capabilities. At the time when we subscribed to PagerDuty, event management …
While more costly than the competitors, PagerDuty has more functionality and is the better tool. There are more integrations, the UI is cleaner, and there are more features and options.
Both the above products (although they could do more, such as alert filtering), were too bulky and cumbersome. Building simple alerts and integrations were time-consuming and more hassle then they should have been. Escalation policies were also difficult and cumbersome to set …
Compared to the companies listed above, PagerDuty was always the stronger contender combined with Datadog. Though now the playing field may have changed since we last did any serious evaluation. PagerDuty has no downtime and "just works". That last phrase is what makes it …
Through our evaluation, we selected PagerDuty, mainly because of its user interface and the ability for support managers to configure it without additional support.
Both VictorOps and PagerDuty do a great job at hands-off alerting people of all their systems neeeds. If used properly it allows everyone, devs, ops, and managers to see into the status of the systems and see what systems and processes need to be improved based upon the types …
We really liked PagerDuty but it got too expensive for us. In my opinion, PagerDuty has a nicer UI/UX and iPhone app as it's done well and has some fun associated with it. However, the pricing model became too expensive for the features we needed. VictorOps is one of several …
The best features of PagerDuty Operations Cloud are that it is a fairly good tool for alerting. Here is how the process works: suppose there is an XYZ server in my environment hosting a production or development application, and a primary on-call engineer has been assigned for that particular week. We have set up monitoring and observability for that node so that if the node is not reachable, an alert is triggered and sends a notification to our integrated Slack channels with PagerDuty Operations Cloud. If the engineer is available, they can acknowledge the alert. If they fail to acknowledge it, the system calls them on their provided number. If that is also not acknowledged, it sends a text message. If those actions are not acknowledged, it sends an alert to the secondary engineer and calls them as well. This multi-channel approach makes it very difficult to miss an important alert or update. PagerDuty Operations Cloud handles this process perfectly, and we do not miss any alerts because of this system.Regarding the stability of PagerDuty Operations Cloud, I cannot recall an incident where it was not available. I can say that it is 100 percent reliable for my needs.
I recommend Splunk on-call is more suited where there are high incident queues; multiple teams need to be involved in handling a P1 severity issue. Multiple levels of escalation are needed environment where automated action is required. I recommend the solution for large-scale & medium-scale business units. For small-scale business units, I see the functional value is less.
From what I have observed, I say customization of notification and alert prioritization are the areas where PagerDuty can be improved. As in our collections team, we also deal with high priority accounts and lower priority system flags, PagerDuty definitely sends the alert, however this sometimes becomes messy. For ex, we had to spend extra time to create multiple escalations and test them in order to handle the priority accounts at first, then others, and that too without overwhelming our team with lower priority notifications.
I would highly recommend PagerDuty if it begins to offer something more intuitive, premium templates.... otherwise it's a great tool, I would say.
The UI is more complex than I would like. Part of the challenge is that most users use PagerDuty infrequently; I don't remember how I changed a policy last time. Another part of the challenge is that some users expect alerting to be a trivial feature, and are reluctant to invest any time in reading the documentation.
PagerDuty is reliable and easy to set up. It gives an effective way to notify the team about critical incidents which results in a faster turnaround time on issues. users can customize their alerts rules based on their preferences. Overall it's effective and easy to use which adds great business value.
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.
OpsGenie was useful, mainly for teams already using Atlassian tools, and xMatters was good for handling team communication during incidents, but PagerDuty felt more complete for managing the full incident process in one place. We went with PagerDuty because it manages alerts, escalations, and on-call duties in a more organized and dependable way, which fits better with how our teams work daily.
Splunk On-Call integrates better with our Splunk Cybersecurity and Reporting products due to the same family tree of the same eco system. We were previously using built-in on-call from individual applications and while adequate, they were difficult to manage and support SLA varied greatly across different applications. In addition we also used xMatters which did not integrate well with SAP products nor Citrix products so we were still using more than a single on-call product which was solved by implementing Splunk On-Call
![Screenshot of Similar Incidents [Apple iPad], Open Incidents [iPhone 8], On-Call Schedule Menu [Apple Watch])](https://media.trustradius.com/product-screenshots/kf/M5/L6SIK3HGD31M.png)
