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's notification process is the most valuable feature."
"A cool feature is that it helps us to understand the flow of the alert. If the alert was coming to the current on-call and he didn't catch the call or didn't notice it for any reason, it starts being escalated automatically, according to the escalation schedule, or to other teammates. You can see the flow very easily on your phone or via the website, if you want to do a post-mortem."
"The most valuable features of PagerDuty are customization, access, policies, and different rules regarding the path of escalation. Additionally, it's easy to use and create overrides. For example, if you all are on a call for one week each, but somebody wants to go on PTO, the team needs to swap shifts in PagerDuty. This is easy to do by creating overrides to switch up the set schedules. It's very user-friendly in that aspect. It works well for monitoring and alerting."
"The initial setup is a simple process."
"The most valuable feature is definitely the flexibility of the schedule. The mobile app is quite also good for what we do: for receiving alerts, acknowledging, assigning, adding new responders. It has rich features for our needs."
"The SMS pages and the mobile application are pretty much the top two features."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"Notification is the most valuable feature."
"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."
"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."
"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 product can be improved by including out-of-the-box integration with other standard tools used in our fields such as Confluence, and Jira."
"It cannot be integrated with our upgraded Jira system."
"They could include incident merging and alert grouping features in the product."
"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's webhooks need some improvement."
"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."
"PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration."
"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."
"The solution can be improved by including a wider list of permissions."
"Should have more YouTube webinars."
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.