We performed a comparison between LogicMonitor 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 plugins are easy to integrate, and LogicMonitor provides these add-ons for vendors like VMware. It becomes very easy to integrate them and take the data sources."
"LogicMonitor saves time in terms of its ability to proxy a connection through a device. For example, if you are troubleshooting a device, which you may want to connect to, you can proxy this connection through the platform. As a support resource, I don't need to use multiple platforms to connect to a device to further investigate the issue. It is all consolidated. From that perspective, it saves time because a resource now only needs to use one platform."
"The solution’s overall reporting capabilities are pretty powerful compared to ones that I have used previously. It seems like it has a lot of customizations that you can put in, but some of the out-of-the-box reports are useful too, like user logon duration and website latency. Those type of things have been helpful and don't require a lot of, if any, changes to get useful content out of them. They have also been pretty easy to implement and use."
"LogicMonitor helps us prevent potential downtime. It's pretty good. It generates low-level warnings that aren't necessarily preemptive but can still alert us to issues we should investigate. These warnings allow us to correlate data and identify areas where we should take action, even if the issues aren't critical."
"LogicMonitor improved on-premises infrastructure monitoring in several ways. One key feature was dynamic resource allocation, although we didn't utilize it much in our system. The main functionalities we benefited from were email alerts, network mapping, and dashboards."
"Whenever we reach out to our customers, we give LogicMonitor as a dashboard to them so they don't need to monitor the hardware side separately. For example, if my service is running on their hardware X, that means they don't need to monitor hardware X and our services too. LogicMonitor has the capability of monitoring their hardware as well as our services. This is how LogicMonitor helps us."
"We only have one monitoring tool, and that is LogicMonitor. It does pretty much everything we need under one roof. They are very good at rapidly releasing new features. It's not like we have to wait six months or a year between new features and data sources. There is very quick development. If there is something that doesn't do it for us, I know I can just raise it with support or our delivery representative, and there is a good chance that that will be looked at. If it's not too much effort, we will see it released in the next few months. So, the solution is very good from that perspective. We have everything in LogicMonitor."
"I really appreciate the reporting function because it allows me to create dashboards that will be emailed to me during the morning so that I have a complete overview of my client's health, within a specific time frame."
"The SMS pages and the mobile application are pretty much the top two features."
"The initial setup is a simple process."
"PagerDuty's best features are the dedicated application that allows me to reach my engineers immediately and the ability to directly assign specific tasks to individuals and have them report back."
"The initial setup is straightforward."
"The most valuable feature is definitely the flexibility of the schedule. The mobile app is quite also good for what we do: for receiving alerts, acknowledging, assigning, adding new responders. It has rich features for our needs."
"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."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"The alerts are immediate in this solution, which allows us to respond to errors quickly."
"LogicMonitor's reporting capabilities definitely could use an improvement. We have made do with the dashboarding and done what we can to make that work for our customers. However, there are definitely customers who would like a PDF or some kind of report along those lines, where we have been utilizing other tools to provide them. The out-of-the-box LogicMonitor reporting is the only thing that we have been less than impressed with."
"Dashboarding capabilities could be enhanced. It is cumbersome, you must do it all at once, and then you must repeat the process every now and then."
"The process of upgrading some of the collectors has been a little bit confusing. I need to understand that better."
"One thing I would like to see is parent/child relationships and the ability to build a "suppression parent/child." For example, If I know that a top gateway is offline and I can't talk to it anymore, and anything that's connected below it or to it is also going to be offline, there is no need to alarm on those. In that situation it should create one ticket or one alarm for the parent. I know they're working towards that with their mapping technology, but it's not quite to that level where you can build out alarm logic or a correlation logic like that."
"LogicMonitor should improve its logging features. It can become expensive and should be cost-effective. It would be great to see prebuilt templates for alerting methods in LogicMonitor that are similar to the prebuilt dashboards. Currently, users have to build their alerting configurations."
"Role-based permissions could be better and updating modules could be smoother."
"LogicMonitor can easily easy to pull data from one item at a time. I have yet to find a good way to get LogicMonitor to show me all the WAN devices and how they're doing in terms of capacity."
"The only functional area I can think of that has room for improvement would be the dashboards. They could use a refresh. It would be nice if there were more widgets and more types of widgets."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"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."
"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."
"I would like to see more content in the notification messages; although, that might be a configuration on our end."
"PagerDuty's webhooks need some improvement."
"The user interface could be more intuitive."
"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."
"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."
LogicMonitor is ranked 7th in AIOps with 25 reviews while PagerDuty Operations Cloud is ranked 8th in AIOps with 35 reviews. LogicMonitor is rated 9.0, while PagerDuty Operations Cloud is rated 8.8. The top reviewer of LogicMonitor writes "We went from nothing to full visibility across our internal and external estates of equipment". 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". LogicMonitor is most compared with ScienceLogic, SolarWinds NPM, Zabbix, OpsRamp and SCOM, whereas PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and Everbridge IT Alerting. See our LogicMonitor 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.