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."PagerDuty let us set up rosters based on our shifts. We could assign a hierarchy for how the calls should be escalated and the number of times the call will be transferred between people before it is answered. It makes it easy to access an agent via mobile phone."
"PagerDuty's notification process is the most valuable feature."
"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 SMS pages and the mobile application are pretty much the top two features."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"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 has scaled well for us."
"The initial setup is a simple process."
"The solution primarily drives system information, and I believe it works fine."
"The monitoring features are the most valuable. We have seen a major benefit from that so far."
"SCOM has helped us to monitor all the VMs in our environment, especially the Windows servers."
"This solution saves us a lot of work because it reduces the effort that is required in order to start monitoring."
"The most valuable feature of SCOM is the capability of using classes within your management pack development."
"It's easy to use."
"It can send messages to our ticketing system."
"The solution has improved our overrides and the ability to start services if they're stopped."
"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."
"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."
"They could include incident merging and alert grouping features in the product."
"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."
"PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration."
"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."
"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."
"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 configurations could be better. There are multiple tests where you can do something, but they can be a trigger as well. The overriding methodologies are not that easy. The configurations are difficult. The configuration and thorough day-to-day operations to get them to the level you want takes some time. It's very difficult."
"The initial setup should be easier to complete."
"I would like to see better support for monitoring Unix-based systems."
"Then there is also an issue with capacity and limited space. That is something that needs to be improved."
"There could be more integration of SIM in the solution."
"The management of the servers could be better."
"It lacks certain details that other products do better, like granular access and better application monitoring."
"Stability and some performance issues exist and they need improvement."
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.
