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 (13th), AIOps (10th), Critical Event Management (CEM) (1st)
Splunk On-Call
Ranking in IT Alerting and Incident Management
13th
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 August 2025, in the IT Alerting and Incident Management category, the mindshare of PagerDuty Operations Cloud is 23.2%, down from 29.1% compared to the previous year. The mindshare of Splunk On-Call is 4.5%, down from 9.1% 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 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."
"PagerDuty's notification process is the most valuable feature."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"PagerDuty helps you bifurcate teams and redirect alerts to specific teams"
"The solution's most valuable features are that it adds each alert as a service, has good scheduling capabilities, and includes the ability to write logic based on texts."
"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."
"It has scaled well for us."
"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."
"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."
 

Cons

"PagerDuty should be integrated with other tools, so it can import the IT roster automatically. Our other rules continue to work once they're configured, but the roster must be added manually."
"It is a very non-customizable product, so you cannot add things like root cause analysis or the classification of incidents based on the area where you are getting more incidents. For example, if you're getting a lot of database issues, that may be an are you want to probe."
"The user interface could be more intuitive."
"It’s quite hard to reach the support team."
"PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration."
"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."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"It cannot be integrated with our upgraded Jira system."
"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."
"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."
 

Pricing and Cost Advice

"The price is very high."
"PagerDuty has monthly and yearly licenses available, the costs of which can get quite high if you have a large number of users."
"There is a license needed to use PagerDuty."
"If we wanted phone calls or additional SMSs, we would have to pitch up for those. They give us so many per month per user, then we have to pay extra if it goes over that."
"The cost is quite high. But if you want to get a full-featured application and you have a big team..."
"If you add more people, then you have to pay more, which is always a thing with the SaaS solutions."
"The pricing may be about $1,000 per user."
"The cost is based on the package you select."
"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.
865,164 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Performing Arts
11%
Financial Services Firm
10%
Manufacturing Company
7%
Computer Software Company
31%
Manufacturing Company
11%
Financial Services Firm
9%
Performing Arts
8%
 

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: July 2025.
865,164 professionals have used our research since 2012.