We performed a comparison between PagerDuty Operations Cloud and SCOM based on real PeerSpot user reviews.
Find out what your peers are saying about PagerDuty, Atlassian, Splunk and others in IT Alerting and Incident Management."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 initial setup is a simple process."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"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."
"The initial setup is straightforward."
"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."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"The product easily integrates with other solutions."
"It can send messages to our ticketing system."
"We are able to do problem determination on runaway processes."
"We have found the scalability capabilities to be okay."
"This solution helps our application teams by allowing them to drill further into issues and perform a root cause analysis."
"SCOM's most valuable features are the network path feature, reporting, and integration with business intelligence."
"The product has helped our organization with in-depth monitoring."
"I like some of their newer features, such as maintenance schedules, because SCOM records SLA and SLO time."
"The product’s auto-remediation feature helps with automation."
"PagerDuty's webhooks need some improvement."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"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."
"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."
"It cannot be integrated with our upgraded Jira system."
"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."
"Regarding certain issues in the solution, it can be difficult to generate reports if we have a program that is not user-friendly for reporting. While this is not necessarily negative, we may need to use another solution."
"Non Windows monitoring is fairly weak. Network device monitoring is not reliable."
"We didn't know the solution enough, and therefore, it took a while to set everything up correctly. There was a learning curve."
"I would like to see more standard libraries for the market solutions, out of the box, that you don't need to do a lot of work on."
"The GI is difficult to work with and the reporting servers are also difficult."
"The initial setup should be easier to complete."
"I would like to better be able to monitor Oracle processes."
"All of the areas of reporting are very bad and need to be improved."
PagerDuty Operations Cloud is ranked 1st in IT Alerting and Incident Management with 35 reviews while SCOM is ranked 3rd in Event Monitoring with 78 reviews. PagerDuty Operations Cloud is rated 8.8, while SCOM is rated 7.8. 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 SCOM writes "Has a good reporting engine, but its monitoring of the cloud-based environment could be improved". PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Everbridge IT Alerting and Splunk On-Call, whereas SCOM is most compared with Dynatrace, Zabbix, Datadog, Nagios XI and ManageEngine OpManager.
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.
