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."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."
"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."
"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 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."
"The alerting would be number one in my book. The thresholds for getting alerts for different criteria are pretty well-thought-out. We don't get many false positives or negatives on the alerting side. If we do get an email alert or some similar alert, we know that it is something that has to be looked at."
"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."
"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."
"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."
"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."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"The SMS pages and the mobile application are pretty much the top two features."
"PagerDuty's notification process is the most valuable feature."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"The product easily integrates with other solutions."
"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 dashboards can be improved. They are good, but there is a pain point. To show things to management, to explain pain points to other customers, to show them exactly where we can do better, the dashboarding could be better. Dashboards need to show the key things. Nobody is going to go into the ample details of Excel sheets or HTML."
"It needs better access for customizing and adding monitoring from the repository. That would be helpful. It seems like you have to search through the forums to figure out what specific pieces you need to get in for specific monitoring, if it's a nonstandard piece of equipment or process. You have to hunt and find certain elements to get them in place. If they could make it a bit easier rather having to find the right six-digit code to put in so it implements, that would be helpful."
"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."
"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."
"Some more application performance type monitoring would be nice. For example, an APM type solution, which would not necessarily completely replace it, but be able to tie into to what we're seeing on the application performance side so we can correlate what's going on with the application versus the underlying infrastructure."
"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."
"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."
"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."
"PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration."
"I would like to see more content in the notification messages; although, that might be a configuration on our end."
"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."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
"They could include incident merging and alert grouping features in the product."
"The user interface could be more intuitive."
"The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue."
"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."
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.