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."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."
"It is easy to set up and monitor an entire facility. This is crucial because we have around 80 facilities that require monitoring. LifePoint is a hub-and-spoke environment, so it is essential to understand all of the WAN interfaces."
"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."
"The concept of developing a dashboard template for ourselves, then cloning it for every single customer, and only having to change one piece of information, is a godsend. That's one of the strengths. We can develop a template that fits every customer and just change the information that is presented."
"LogicMonitor added AI technology to help understand what's normal and that has helped quite a bit, so that's the feature I found most valuable in the product. The product is also doing quite well with identifying devices and customizing a particular Cisco version or model number. LogicMonitor continues to be active in updating what is available to be monitored, and it's been very good with keeping those things current, so that's another valuable feature of the product."
"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."
"The most valuable feature is the visualization of the data that it is collecting. I have used many products in the past and they tend to roll up the data. So, if you're looking at data over long periods of time, they start averaging the data, which can skew the figures that you're looking at. With LogicMonitor, they have the raw data there for two years, if you are an enterprise customer. If you are looking at that long duration of data, you're seeing exactly what happened during that time."
"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."
"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 inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"The initial setup is a simple process."
"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."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"It has scaled well for us."
"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."
"There is a lack of automation, especially in terms of remediating problems. The problem is seen and identified, but there is a need and a gap where LogicMonitor can help us automate the remediation of the problem."
"Automated remediation of issues has room for improvement. I don't know how best to handle it, but I know that they're kind of working on it. I know there are some resources that can do automated remediation. I would like them to improve this area so it could be completely hands-free, where it detects an issue, such as, if a CPU is running high. There are ways to do it even now, but it's a bit more involved."
"LogicMonitor should always improve AI because we are always striving for real intelligence. An additional feature we'd like to see in the next release of LogicMonitor is more in the area of identification of when the dominant workload is working. There are certain devices and applications that have cycles of their own. Some are used primarily during prime time, and some are used during the overnight timeframe, and better identification and classification of those workloads would be helpful. For example, we could then do some more planning about, for this particular set of devices, as it has a prime time environment, and we don't want to see a 24-hour average, as we want to see what is the 75th or 90th percentile utilization during the prime time when it is being used, whenever that prime time is."
"One drawback of LogicMonitor is its licensing model, which requires an additional license for each module. For example, if you need to use Azure monitoring, you'll need an additional license on top of the base license."
"One thing that could be really better is the mapping. Auvik is really good at it. They have a really nice way to give you a visual representation of your network, but in LogicMonitor, this functionality is not as powerful and as good as Auvik."
"There are some very specific things that need improvement in LogicMonitor. One is the lack of formatting for customized alerts, particularly the delivery of them to our email channel. We'd also like to see further customization of dashboards. Finally, something that is specific to us as an MSP that uses LogicMonitor, is white-labeling or skinning of the product, so we can make it look more customer-focused for our customers."
"We are working with LogicMonitor to get flexibility to see the absolute running numbers, rather than doing an average. They can keep the average for customers who want it, but there should be a way to at least show the real numbers, which are coming every second on the screen."
"The process of upgrading some of the collectors has been a little bit confusing. I need to understand that better."
"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’s quite hard to reach the support team."
"I would like to see more content in the notification messages; although, that might be a configuration on our end."
"PagerDuty can improve the integration with Terraform."
"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."
"Something that needs to be improved, is adding multilingual support."
"The user interface could be more intuitive."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
LogicMonitor is ranked 8th in AIOps with 25 reviews while PagerDuty Operations Cloud is ranked 7th 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 SolarWinds NPM, ScienceLogic, Zabbix, SCOM and OpsRamp, 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.
