No more typing reviews! Try our Samantha, our new voice AI agent.

Opsgenie vs PagerDuty Operations Cloud vs Splunk On-Call comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

Mindshare comparison

As of September 2026, in the IT Alerting and Incident Management category, the mindshare of Opsgenie is 5.8%, down from 13.3% compared to the previous year. The mindshare of PagerDuty Operations Cloud is 7.6%, down from 22.2% compared to the previous year. The mindshare of Splunk On-Call is 3.5%, down from 4.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Alerting and Incident Management Mindshare Distribution
ProductMindshare (%)
PagerDuty Operations Cloud7.6%
Opsgenie5.8%
Splunk On-Call3.5%
Other83.1%
IT Alerting and Incident Management
 

Featured Reviews

Pramodh M - PeerSpot reviewer
DevSecOps Consultant at a tech services company with 51-200 employees
Offers different levels of notification options, including WhatsApp integration
Opsgenie has been most valuable in managing our incident response. We use Opsgenie for on-call management of AWS services, and its integration with CloudWatch has been particularly beneficial. Opsgenie alerts us to anomalies in cloud services, not just incidents but also performance issues like delayed response times or execution errors. So, we will quickly know about the issue, and it allows us to take swift action. It has been very helpful to us. Opsgenie's strength lies in its configurable alerting levels, from first responders to escalation managers. It offers different levels of notification options, including WhatsApp integration, ensuring timely alerts to the relevant team members. We also use the on-call scheduling feature. It is easy to use. The on-call scheduling feature is user-friendly and easily integrates with our existing systems, streamlining schedule management without added complexity.
reviewer2879727 - PeerSpot reviewer
Cloud Dev Ops Engineer at a tech vendor with 10,001+ employees
Unified incident response has reduced alert noise and improves on-call focus and coordination
PagerDuty Operations Cloud could improve its noise reduction by making deduplication and suppression more automated instead of manually tuned, and the service dependency graph could be more intuitive with cleaner visuals and easier-to-understand root cause tracing during major incidents. Automation could go further with smarter runbook triggers and AI-driven suggestions to help find root causes, which could save a lot of time for engineers who are struggling to understand what is actually happening. These AI capabilities could lower the time by maybe 50–60%. Analytics and reporting could be more flexible, allowing custom dashboards and filters and team-level MTTA and MTTR breakdowns, so that it is segregated based on teams and it is much easier to have custom dashboards for the teams to understand more. Alert storms were a recurring frustration for the on-call team, and escalation overrides and service dependency graphs can get a bit confusing in larger environments. More customizable analytics and smarter automation would make the platform even easier, more flexible and more powerful for the team to understand. PagerDuty Operations Cloud could improve its analytics flexibility with customized dashboards and AI capabilities to be more trained and more reliable. Service dependency mapping can also feel cluttered in big environments, making it harder to trace upstream and downstream impacts during bigger incidents. We implemented PagerDuty Operations Cloud's AI to help with alert grouping and early incident insights, but accuracy was not consistent enough to rely on during critical events. It occasionally grouped unrelated alerts or missed correlations, which limited the operational efficiency gains we expected. The on-call team still depended heavily on manual triage because AI suggestions were not always aligned with the real root cause. Overall, AI added some value but it has not yet reached the reliability needed to significantly improve the incident response efficiency. It needs more training or more work.
Ramani Happy - PeerSpot reviewer
Dev Ops Engineer at Data Elicit Solutions Pvt. Ltd.
Streamlined incident response has reduced downtime and improved on-call collaboration
A few things I would improve in Splunk On-Call. Honestly, the reporting and analysis side feels a bit weak. If I want to deep dive into the on-call load, including MTTD and MTTR rates, I kind of have to export data and build my own dashboard, which is not as out-of-the-box as I would prefer. The UI has improved, but it still feels a little chunky in certain areas, particularly when managing schedules. When I have a lot of teams, it can get messy. Additionally, the pricing model is per user, which starts to get expensive as the team scales.

Quotes from Members

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

Pros

"Opsgenie has streamlined our communications and alerting."
"The integration feature is the most valuable. It provides a lot of customizations for the integrations we use."
"OpsGenie has many features, such as email notification, SMS notification, roster, tracking of the tickets. Automation, like scripting, is also possible. There are also features for maintaining the history of the tickets and all the solutions related to how it was resolved previously. If there are similar kinds of tickets, we can look at how a person is working on that ticket. If he doesn't have any idea, you can look back at a similar ticket and solve it as the previous person did it."
"Opsgenie is easy to configure and use."
"We went with OpsGenie because it was simpler to integrate with Atlassian products."
"Opsgenie integrates with Atlassian and other web monitoring and incident management tools."
"One of the features my team found valuable in Opsgenie is the alert. There's also the option to install an app on your phone, so even if you don't have any mobile reception, but you're still connected to WiFi, you still get the alerts via the app, not just via phone call or SMS. The combination of both options was very useful because sometimes you have data and you don't have coverage by mobile, or vice versa. To have both options in terms of receiving alerts was very useful. Another valuable feature of Opsgenie is the on-call rotation with alerts. I belonged to a small team of three, then the team expanded into four members where everyone was on a weekly on-call basis, with each team member having a week of being on-call. At first, it was a bi-weekly on-call rotation, then it became once every three weeks, and after that, it was once every four weeks, so the on-call rotation with an alert feature was useful. My previous company had two separate environments, on the cloud and on-premises. My team was in charge of the on-premise environment, so there was a queue for my team with everything in Opsgenie, then the DevOps team had its queue on a group of infrastructure related to the cloud. Each team had its own devices organized in a group that was only managed per team. The on-call rotation was also separated between groups. Opsgenie is a very convenient solution for both teams in my previous company."
"Opsgenie has been most valuable in managing our incident response. We use Opsgenie for on-call management of AWS services, and its integration with CloudWatch has been particularly beneficial. Opsgenie alerts us to anomalies in cloud services, not just incidents but also performance issues like delayed response times or execution errors. So, we will quickly know about the issue, and it allows us to take swift action. It has been very helpful to us."
"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 Operations Cloud positively impacts our organization by helping us increase the overall SLA delivery; earlier, we were having a delivery count of 87% or 88%, but after setting up PagerDuty Operations Cloud, we were able to achieve the SLA up to 99.5% post-installation."
"PagerDuty Operations Cloud delivers very high performance when notifying users, especially in high-frequency trading environments where even a second of delay can result in billion or trillion dollar transaction losses."
"PagerDuty Operations Cloud is the best tool available, and I can confidently say it is the best tool for all aspects, not just incident management or escalation, but for all analytical functions as well."
"PagerDuty Operations Cloud offers the important advantage that we can easily get notified and work on alerts and system degradation within our RPO and RTO targets."
"Using PagerDuty Operations Cloud is a very crucial part for us; if we do not use it, we don't know what is happening in the customer's environment."
"PagerDuty Operations Cloud has positively impacted our organization by allowing us to be immediately paged when a system or service is down, enabling us to quickly respond and provide updates to the organization on issues and their resolution."
"The flexible schedule is the most valuable feature. It was very easy to set out a rotation."
"I would recommend VictorOps for global distributed support teams."
"VictorOps has been good enough for us and it's effective for our needs in case of an on-call escalation process."
"We are very satisfied with the tool."
"Since implementing Splunk On-Call, our mean time to acknowledge has dropped significantly, and we have fewer escalations to senior engineering for things that could have been caught earlier."
"Splunk On-Call has helped my organization to improve response times, reduce missed alerts, and coordinate teams more efficiently during incidents."
"My VP of Operations is ecstatic about the VictorOps product."
"VictorOps has decreased the meantime to acknowledge an incident management process, our developers can be on-call faster when we are using this solution, and we can fix our incidents much quicker."
 

Cons

"The handshake with the monitoring tools can also be improved. When there were a bunch of alerts or the number of alerts was more than a thousand in a minute, OpsGenie wasn't able to handle everything properly. The handshake issues were there."
"I would like to see a little bit more work in API key management in the Opsgenie UI. It's a bit difficult to manage sometimes. For example, in terms of management, you can either see all the keys or none of the keys. This is something for which I would like to have better granularity so that I could give some people access to some of the keys. It's something that I don't have today if I'm not mistaken."
"The installation of other applications is difficult in Opsgenie. I would like to see more flexible reporting methodologies. Scalability and pricing also need to be improved."
"Initially, Opsgenie had bidirectional integration with Jira Service Management, but that functionality has been scaled back. Previously, Opsgenie was adept at managing incidents within its ecosystem, offering seamless ticket transfers between Opsgenie and Jira Service Desk. I valued the ability to push tickets between the two platforms, addressing the need for widespread information accessibility, though it sometimes led to duplication. My suggestion would be to reintroduce complete ticket funneling between these systems to streamline operations."
"In a future release, we would like to receive alerts when a specific threshold is reached and to escalate the reason for that alert."
"We are using the cloud version of Atlassian products now, but I think the Data Center version we used earlier was much more user-friendly. There are lots of limitations in the cloud version The add-on or features that work with the Data Center versions are not compatible with the cloud version."
"It should also come with cloud integrations, which are not that great with OpsGenie as of now."
"Typically, the alerts are vague at times, and when the automated callers begin reading that alert, it does not make sense to us."
"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."
"In terms of witnessing an ROI, no one has really done that level of due diligence."
"I would defiantly like to see more integration with other systems. This would really add some value for us."
"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."
"PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration."
"It cannot be integrated with our upgraded Jira system."
"Because of the way you have to structure the rosters, if an engineer has to go on leave, you can't just go in and reassign or take this person out of all of the different rosters that they're in."
"The noise aspect of PagerDuty Operations Cloud could be better."
"We chose to move away from the HP product as far as our monitoring goes and dealing with system-generated alerts, simply because it took too much time and effort to manage the APM platform."
"A few things I would improve in Splunk On-Call. Honestly, the reporting and analysis side feels a bit weak."
"I would say a little bit of the user experience and the user interface of Splunk On-Call can be improved."
"The third-party configuration tool could be easier to use."
"One area for improvement would be enhancing the mobile app experience."
"The solution can be improved by including a wider list of permissions."
"The only feature that we are currently waiting on right now is really kind of an annoyance factor: when we get on the timeline on the main dashboard, there’s an ACK All button."
"Should have more YouTube webinars."
 

Pricing and Cost Advice

"The pricing is on the lower side; I would rate it a six out of ten, with ten being low price, which indicates good affordability."
"The cost of the solution depends on the package you select and is per user."
"The pricing is fine. I would rate the pricing a six out of ten, with one being high price and ten being low price."
"Integration with other solutions is one of the most valuable features of Opsgenie."
"I rate Opsgenie eight out of 10 for affordability. Opsgenie is on the cheaper side, and it fits our budget. I estimate the license costs around $400 to 500 annually for 15 users. The price is available on the internet. It's a standard, straightforward price."
"From the pricing perspective, they are on the higher side as compared to other competitors."
"I'm not the person who dealt with Opsgenie in terms of pricing, and I don't know how the solution compares to other solutions in the market, price-wise. I won't be able to say if it gives you the best value for money or not, but if Opsgenie gives good value for money, then I don't see a reason why you shouldn't use it."
"The solution's prices are exorbitant."
"If you add more people, then you have to pay more, which is always a thing with the SaaS solutions."
"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."
"Licensing costs are around $700 a month, and the only additional costs, are phone costs in some instances."
"The solution is paid on a monthly basis and represents about 1% of the platform's budget."
"The cost is quite high. But if you want to get a full-featured application and you have a big team..."
"There is a license needed to use PagerDuty."
"The cost is based on the package you select."
"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.
914,322 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Performing Arts
12%
Financial Services Firm
8%
Transportation Company
8%
Comms Service Provider
6%
Outsourcing Company
11%
Financial Services Firm
11%
Performing Arts
10%
Manufacturing Company
9%
Retailer
15%
Construction Company
10%
Outsourcing Company
10%
Financial Services Firm
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise5
Large Enterprise6
By reviewers
Company SizeCount
Small Business32
Midsize Enterprise25
Large Enterprise79
By reviewers
Company SizeCount
Small Business1
Midsize Enterprise1
Large Enterprise10
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for PagerDuty?
I am not current on what the current pricing is for PagerDuty Operations Cloud, but I assume it is per seat and per r...
What needs improvement with PagerDuty?
The users would complain that they always had a hard time maintaining their schedules, their escalations, and install...
What is your primary use case for PagerDuty?
The usual use cases for PagerDuty Operations Cloud include incident management. I ran the infrastructure teams and SR...
What is your experience regarding pricing and costs for VictorOps?
I would say it is very affordable. I have compared Splunk On-Call internally with our own homemade solution. I have a...
What needs improvement with VictorOps?
I would say a little bit of the user experience and the user interface of Splunk On-Call can be improved. I have alre...
What is your primary use case for VictorOps?
I am currently working with Splunk Cloud, but I could review Splunk Enterprise as well because it is fundamentally th...
 

Also Known As

No data available
No data available
VictorOps
 

Overview

 

Sample Customers

2500+ customers including Yahoo, Politico, Dynatrace, Looker, Solarwinds, Overstock, Oregon State University, Glassdoor, Cloudticity, Unbounce, Bleacher Report
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, Splunk, SolarWinds and others in IT Alerting and Incident Management. Updated: August 2026.
914,322 professionals have used our research since 2012.