We performed a comparison between PagerDuty Operations Cloud and Splunk On-Call based on real PeerSpot user reviews.
Find out in this report how the two IT Alerting and Incident Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."PagerDuty is very stable and very reliable."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"PagerDuty let us set up rosters based on our shifts. We could assign a hierarchy for how the calls should be escalated and the number of times the call will be transferred between people before it is answered. It makes it easy to access an agent via mobile phone."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"The alerts are immediate in this solution, which allows us to respond to errors quickly."
"Notification is the most valuable feature."
"PagerDuty's best features are the dedicated application that allows me to reach my engineers immediately and the ability to directly assign specific tasks to individuals and have them report back."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
"The most valuable feature of the solution is helpdesk escalation."
"Transmogrifier and automatic solution report gives me a report with the solution and the way to solve issues when an error occurred."
"The alert calling feature is the best because notifications are delivered via phone messages."
"The flexible schedule is the most valuable feature. It was very easy to set out a rotation."
"Because of the way you have to structure the rosters, if an engineer has to go on leave (or something), you can't just go in and reassign/take this person out of all of the different rosters that they're in. You have to go into each of the rosters and take them out. There might be a roster for business hours, after hours rotation, and monitoring deployments. Each time we need to take an engineer out of the pool, e.g., if they're sick or on leave, then we have to go and touch all of those rosters, updating and replacing them. Whereas, if we could just take the person out and have it automatically fill in the rostering, then that would make life a lot easier for managing it."
"The On-Call Teams feature could be better in terms of levels of conditions related to which team or member should get the responsibility of handling a matter or incident."
"The biggest area for improvement with PagerDuty is noise suppression. There have been a handful of incidents through our use of PagerDuty over the years where one incident may lead to 30 to 50 pages because you're monitoring all these different things, and each thing is an individual page. There should be the ability to set up paging tiers and group correlations between some of the different pages. That is something that would be really valuable. We should be able to say this one page may have a group or a tree of effective other pages that may tier off of it. So, if you see those pages independently, go ahead and alarm, but if you see this plus that, don't do that."
"Something that needs to be improved, is adding multilingual support."
"The solution's analytics are okay. I don't think the features, at this point, give you a lot of insights. We have actually been trying to get insights from it but it hasn't really given us a lot of extra points to explore. We were looking at the number of alerts to see where many of the alerts were coming from. We never managed to get many insights on this."
"The product can be improved by including out-of-the-box integration with other standard tools used in our fields such as Confluence, and Jira."
"The user interface could be more intuitive."
"The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue."
"The solution can be improved by including a wider list of permissions."
"Should have more YouTube webinars."
"At that stage, all our needs are fulfilled, but at the beginning, we had some feature requests and they were deployed during their roadmap."
"There could be improvements with communicating an incident or alert."
"The third-party configuration tool could be easier to use."
PagerDuty Operations Cloud is ranked 1st in IT Alerting and Incident Management with 35 reviews while Splunk On-Call is ranked 8th in IT Alerting and Incident Management with 10 reviews. PagerDuty Operations Cloud is rated 8.8, while Splunk On-Call is rated 8.6. The top reviewer of PagerDuty Operations Cloud writes "Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure". On the other hand, the top reviewer of Splunk On-Call writes "Allows us to create flexible schedules for on-call rotations". PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Everbridge IT Alerting and xMatters , whereas Splunk On-Call is most compared with Opsgenie, New Relic, Everbridge IT Alerting, xMatters and JIRA Service Management. See our PagerDuty Operations Cloud vs. Splunk On-Call report.
See our list of best IT Alerting and Incident Management vendors.
We monitor all IT Alerting and Incident Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.