We performed a comparison between Moogsoft and PagerDuty Operations Cloud 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."The solution is extremely helpful with correlating IP failures and it has a very good sort of flow chart of IP systems. For example, if you see a failure in system A, you can track it down to the system causing the issue. This is a very handy feature."
"Moogsoft is easily deployable and ready to use."
"The Event Management feature is quite valuable."
"Moogsoft AIOps integrates seamlessly with 50-plus IT monitoring, automation, service management, notification, and collaboration tools. It also provides a great and easy-to-use interface for observing."
"I like the prediction features."
"Incident management is streamlined with Moogsoft. One standout feature is its unique situation-creation capability, differentiating it from other fault management tools. While other tools typically convert alarms directly into tickets or incidents, Moogsoft adds a middle layer where multiple alarms can be aggregated into one incident. Moogsoft's strong AI capabilities also allow it to correlate similar alarms automatically based on past experiences."
"The product currently seems to be a few steps ahead of the competition."
"Moogsoft's most valuable features are event management, correlation, and observability."
"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 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."
"The SMS pages and the mobile application are pretty much the top two features."
"A cool feature is that it helps us to understand the flow of the alert. If the alert was coming to the current on-call and he didn't catch the call or didn't notice it for any reason, it starts being escalated automatically, according to the escalation schedule, or to other teammates. You can see the flow very easily on your phone or via the website, if you want to do a post-mortem."
"The product easily integrates with other solutions."
"It has scaled well for us."
"The alerts are immediate in this solution, which allows us to respond to errors quickly."
"The initial setup is straightforward."
"I would like to see additional reports or information on the dashboard that includes metrics about CPU usage and memory."
"I would like to see how Moogsoft integrates with the multi-cloud and brings out a single pane of glass, to see everything on one screen."
"Moogsoft is dependent on external products to do orchestration and SOP-based functionality."
"Some additional API interfacing would be great to enable getting the data out of AIOps programmatically."
"It is taking a long time to set it up and could do more to roll out quickly."
"The documentation and flexibility for generic integration could be improved."
"They are very much dependent on open-source technologies like RabbitMQ message bus. They are using open-source databases, Apache Tomcat, NGINX. If we face any issues with Apache Tomcat or the RabbitMQ message bus, then we do not get support from them. We have to troubleshoot it ourselves."
"I would like to see more integrations. It is rather difficult to install the enterprise systems with the agents."
"Something that needs to be improved, is adding multilingual support."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"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."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
"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."
"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."
"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."
"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."
Moogsoft is ranked 13th in AIOps with 11 reviews while PagerDuty Operations Cloud is ranked 8th in AIOps with 35 reviews. Moogsoft is rated 7.6, while PagerDuty Operations Cloud is rated 8.8. The top reviewer of Moogsoft writes "A cost-efffective cloud solution for noise filtration but needs enhanced interfaces". On the other hand, the top reviewer of PagerDuty Operations Cloud writes "Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure". Moogsoft is most compared with ServiceNow IT Operations Management, OpsRamp, BigPanda, Dell CloudIQ and Zabbix, whereas PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Everbridge IT Alerting and Splunk Enterprise Security. See our Moogsoft vs. PagerDuty Operations Cloud 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.