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."
"It reduces the amount of white noise. If something comes through, then it will alert somebody. However, if it's a bit of white noise that comes through at night, then it gets dealt with the next day. Everything is visible to everybody. It's not just a single person getting an SMS, then going, "Oh, I'm not going to worry about that." The visibility to everybody on the team is one of the great things about it because it reduces the white noise."
"Notification is the most valuable feature."
"The most valuable feature is the phone app that allows us to send notifications without the additional fees when sending by SMS or phone calls."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"The product easily integrates with other solutions."
"PagerDuty's notification process is the most valuable feature."
"The initial setup is a simple process."
"The most valuable feature of the solution is helpdesk escalation."
"The flexible schedule is the most valuable feature. It was very easy to set out a rotation."
"The alert calling feature is the best because notifications are delivered via phone messages."
"Transmogrifier and automatic solution report gives me a report with the solution and the way to solve issues when an error occurred."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
"Something that needs to be improved, is adding multilingual support."
"There is room for improvement with the time schedule. The way the schedule currently works is you assign all the team members in one schedule and it automatically spreads them around throughout the schedule... It would be better to be able to edit the schedule and place my team members where I want, or at least to have that option in addition to the automatic process."
"The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue."
"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 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."
"The user interface could be more intuitive."
"I would like the UI to be more intuitive. I would like to be able to group or color-code the discoveries. When you create a system, you have a listing of all the different configurations. You can list them by teams, but some additional color coding would be helpful. I would break it down by incident controls. In other words, it should be broken down it into response teams and engineering divisions."
"PagerDuty can improve the integration with Terraform."
"The third-party configuration tool could be easier to use."
"There could be improvements with communicating an incident or alert."
"At that stage, all our needs are fulfilled, but at the beginning, we had some feature requests and they were deployed during their roadmap."
"Should have more YouTube webinars."
"The solution can be improved by including a wider list of permissions."
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, JIRA Service Management and xMatters . 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.