We performed a comparison between PagerDuty Operations Cloud and Sumo Logic Observability based on real PeerSpot user reviews.
Find out in this report how the two AIOps solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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."
"Notification is the most valuable feature."
"The SMS pages and the mobile application are pretty much the top two features."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"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."
"It has scaled well for us."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"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."
"Alerting and consistency are key. We have different tiers with log collectors, and continuous querying provides near-real-time updates. It's almost like instantly when something happens, like pending transactions or error fees. This helps reduce incident resolution time compared to waiting for thresholds on other platforms. We can continue logging in with them seamlessly and quickly get into action."
"I have not seen any stability issues in the product."
"The product is easy to learn."
"Sumo Logic Observability presents a range of valuable features, including well-crafted dashboards and a diverse selection of helpful apps. However, personally, I don't hold a favorable opinion of the solution. While I don't struggle with writing queries, my main difficulty lies in recruiting competent individuals and ensuring their proficiency in utilizing the solution. This often leads to additional challenges and complexities. From my perspective, when compared to Microsoft Sentinel or even Splunk, Sumo Logic Observability has a steeper learning curve. One contributing factor to this disparity is the solution's long existence in the market compared to Synlogic. Nevertheless, I acknowledge that there are capable and knowledgeable professionals employed at Sumo Logic Observability. The effectiveness of the solution largely depends on how it is integrated into your internal operations and environment. Its utility and benefits can vary significantly. It is worth noting that organizations like the NSA and, I believe, the CIA used it in the past, primarily for rapidly searching and analyzing large volumes of data. To leverage its capabilities effectively, you must determine how to tailor it to your specific needs."
"The solution allows multiple groups to converge on a unified platform, allowing for different utilization by various teams."
"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."
"Something that needs to be improved, is adding multilingual support."
"The user interface could be more intuitive."
"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."
"It cannot be integrated with our upgraded Jira system."
"It’s quite hard to reach the support team."
"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."
"Documentation could be better. While it's generally good, sometimes finding what you need requires extensive searching. It's not always clear where to look for specific things."
"SearchUI.exe is a bit clunky in the product, making it an area where the product needs improvements."
"Fine-grained data can be quite frustrating to work with and should be made easier."
"Implementing a more streamlined enrichment process, and conceptualizing the observability data collection as an ETL pipeline would be helpful."
PagerDuty Operations Cloud is ranked 8th in AIOps with 35 reviews while Sumo Logic Observability is ranked 12th in AIOps with 5 reviews. PagerDuty Operations Cloud is rated 8.8, while Sumo Logic Observability is rated 8.0. 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 Sumo Logic Observability writes "Easy creation of custom fields, no need to alter applications; supports ten active logging applications simultaneously and faster than aster than default search tools". PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and Everbridge IT Alerting, whereas Sumo Logic Observability is most compared with Dynatrace, New Relic, Prometheus and Chronosphere. See our PagerDuty Operations Cloud vs. Sumo Logic Observability report.
See our list of best AIOps vendors.
We monitor all AIOps 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.
