Try our new research platform with insights from 80,000+ expert users

PagerDuty Operations Cloud vs Splunk On-Call comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 2, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

PagerDuty Operations Cloud
Ranking in IT Alerting and Incident Management
1st
Average Rating
8.8
Reviews Sentiment
7.3
Number of Reviews
37
Ranking in other categories
Process Automation (14th), AIOps (9th), Critical Event Management (CEM) (1st)
Splunk On-Call
Ranking in IT Alerting and Incident Management
12th
Average Rating
8.6
Reviews Sentiment
6.9
Number of Reviews
10
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the IT Alerting and Incident Management category, the mindshare of PagerDuty Operations Cloud is 21.4%, down from 30.0% compared to the previous year. The mindshare of Splunk On-Call is 5.1%, down from 10.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Alerting and Incident Management
 

Featured Reviews

JeremyEmmett - PeerSpot reviewer
Centralized alert management with customizable routing and superior scheduling
Everything can always be better. Operations are somewhat limited by their integration package. For example, integrating with Jira was problematic until they updated to a better plug-in. The ability to build customized modules would be advantageous, allowing organizations to define their own integration modules. It would be useful to have a way to define all configurations in code that is similar to how Terraform operates.
Wojtek Witowski - PeerSpot reviewer
Allows us to create flexible schedules for on-call rotations
For alerts, we could choose to get a text message, app notification, or a phone call. The phone calls were very unusable, because it just read a bunch of numbers, like an ID of the alert. If there was a way to customize the phone call message, that would be great. Later, we would try to read the message, but it wasn't great at reading that. They had some sort of internal chat functionality where if we got an alert, we could write to somebody else and ask them for help, but that was super cumbersome. There could be improvements with communicating an incident or alert. Imagine you call the help desk and you say that your computer is broken and then they say, "Actually, the internet is broken, so let us forward your alerts to the network people." And the network people say, "Actually, the electricity is the problem, so let us forward it to the electricity people." Basically, you could send the alert between the support teams inside the company.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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."
"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."
"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 feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"It integrates with multiple applications and is highly customizable, with policies, escalation procedures, and an event routing tool that ensures contacting the right person."
"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."
"The alerts are immediate in this solution, which allows us to respond to errors quickly."
"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 flexible schedule is the most valuable feature. It was very easy to set out a rotation."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
"The alert calling feature is the best because notifications are delivered via phone messages."
 

Cons

"The user interface could be more intuitive."
"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 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."
"It cannot be integrated with our upgraded Jira system."
"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."
"PagerDuty can improve the integration with Terraform."
"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."
"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."
"There could be improvements with communicating an incident or alert."
"Should have more YouTube webinars."
"The third-party configuration tool could be easier to use."
"At that stage, all our needs are fulfilled, but at the beginning, we had some feature requests and they were deployed during their roadmap."
"The solution can be improved by including a wider list of permissions."
 

Pricing and Cost Advice

"The solution is paid on a monthly basis and represents about 1% of the platform's budget."
"There is a license needed to use PagerDuty."
"The price is very high."
"The cost is based on the package you select."
"If you add more people, then you have to pay more, which is always a thing with the SaaS solutions."
"PagerDuty has monthly and yearly licenses available, the costs of which can get quite high if you have a large number of users."
"The cost is quite high. But if you want to get a full-featured application and you have a big team..."
"They're very good in pricing compared to the competitors in the area. I would rate them a five out of five in terms of pricing."
"The price of the solution could be less expensive."
report
Use our free recommendation engine to learn which IT Alerting and Incident Management solutions are best for your needs.
850,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
12%
Manufacturing Company
7%
Healthcare Company
6%
Computer Software Company
33%
Manufacturing Company
11%
Financial Services Firm
11%
Government
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about PagerDuty?
The product easily integrates with other solutions.
What is your experience regarding pricing and costs for PagerDuty?
The solution was expensive, but if all its features were utilized, it was considered worth the cost. The tier-based pricing model was cumbersome, and there was a desire for a service-based catalog ...
What needs improvement with PagerDuty?
Everything can always be better. Operations are somewhat limited by their integration package. For example, integrating with Jira was problematic until they updated to a better plug-in. The ability...
Ask a question
Earn 20 points
 

Also Known As

No data available
VictorOps
 

Overview

 

Sample Customers

40% of the Fortune 100 TrustPagerDuty. Customers include: Slack, Intuit, Zendesk, Panasonic, Pinterest, Airbnb, eHarmony, McKesson, Comcast
NVIDIA, Cisco, NBC, Rackspace, Intuit, DirectTV, NASCAR, Arrow Electronics, Alliance Health, NetApp, Edmunds, New York Times, Return Path, Sony Playstation, CA Technologies, Sphero, Symantic, HBO, Weatherford, Blackboard, Epic Games
Find out what your peers are saying about PagerDuty Operations Cloud vs. Splunk On-Call and other solutions. Updated: April 2025.
850,747 professionals have used our research since 2012.