Try our new research platform with insights from 80,000+ expert users

LogicMonitor vs PagerDuty Operations Cloud comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 16, 2024
 

Categories and Ranking

LogicMonitor
Ranking in AIOps
5th
Average Rating
9.0
Number of Reviews
26
Ranking in other categories
Network Monitoring Software (12th), IT Infrastructure Monitoring (11th), Container Monitoring (5th), Cloud Monitoring Software (13th)
PagerDuty Operations Cloud
Ranking in AIOps
13th
Average Rating
8.8
Number of Reviews
36
Ranking in other categories
Process Automation (15th), IT Alerting and Incident Management (1st), Critical Event Management (CEM) (2nd)
 

Featured Reviews

Henry-Steinhauer - PeerSpot reviewer
Sep 21, 2022
They have an active community of users who are willing to share their experiences and how they have extended the solution to do unusual things.
We are a network of hospitals using the solution to monitor our network devices and all of the interfaces connected to them. It's predominantly instances of applications running on Windows Server. We use the Windows WMI for Windows Server stats. The IT directors at our hospitals use it, so we have…
Ashish  Paikrao - PeerSpot reviewer
Sep 8, 2023
Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure
We were exploring ManageEngine ServiceDesk. So, we need a feature where we can, like, when an alert triggers, we should alert the recipient by on-call. So, when an alert is detected, a ticket is generated in the management team, and we want to notify them on-call. Like, this ticket has been generated and stuff. So, I would like to see a similar feature in this solution. This is why we want an alternative to PagerDuty. We want an alternative to PagerDuty. So we are getting on-call notifications using PagerDuty, but now we want to replace PagerDuty with ManageEngine ServiceDesk. So whenever some incident happens in the cloud infrastructure, we get data alerts from cloud security. We want to integrate a service that will provide us with notifications on-call. That this server is down, or this website is down, or this thing is going wrong. Another area of improvement is integration. It cannot be integrated with our upgraded Jira system. That's why we are dropping PagerDuty. We won't continue using it due to integration issues.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"We get full visibility into whatever the customer wants us to monitor and we get it pretty rapidly. That is very important. Only having certain metrics that other platforms will give you out-of-the-box means you only get a small picture, a thumbnail picture. Whereas with LogicMonitor, you get the entire "eight by 10 picture", out-of-the-box. Rather than some availability metrics, you get everything. You get metrics on temperature, anything related to hardware failure, or up and down status."
"LogicMonitor is good for getting a full view of your topologies. They have LiveMaps, which give you a visual representation of your infrastructure."
"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."
"One thing that's very valuable for us is the technical knowledge of the people who work with LogicMonitor. We looked at several products before we decided to use LogicMonitor, and one of the key decision-making points was the knowledge of the things that they put in the product. It provides real intelligence regarding the numbers that you see on the product, which makes it easy for us technical people to troubleshoot. Other products don't provide you with such information. You see a value going up, but you don't know what it means. LogicMonitor provides such information. For instance, if a value goes up, it says that it is probably because your disk area was too low."
"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 most valuable feature of LogicMonitor is the infrastructure monitoring capability."
"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."
"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."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"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."
"PagerDuty's notification process is the most valuable feature."
"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."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"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."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
 

Cons

"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."
"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."
"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."
"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."
"Role-based permissions could be better and updating modules could be smoother."
"We would like to see more functionality around mapping of topologies, in terms of networks. An improvement that we would like to see is added functionality to get more detail out of mapping. For example, if the LogicMonitor Collector identifies a connection between two network endpoints, it would be great to actually see which ports are connecting the two endpoints together. That functionality is something we greatly desire. It would actually make our documentation more dynamic in the sense that we wouldn't need to manually document. If this is something that the platform could provide, then this would be a great asset."
"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."
"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."
"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."
"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."
"PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration."
"The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue."
"I would like to see more content in the notification messages; although, that might be a configuration on our end."
"The user interface could be more intuitive."
"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."
"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."
 

Pricing and Cost Advice

"It's affordable. The price we get per license is a lot cheaper than what we were getting with some of the other tools. There are other monitoring tools out there that are cheaper, but what you get with LogicMonitor, out-of-the-box, makes it worth the cost."
"It definitely pays for itself in the amount of time we're not spending with false errors or things that we haven't quite dealt with monitoring. It has been good cost-wise."
"As a managed service provider, we have the highest level of licensing that they offer, so we don't have any extra fees. I believe there are some add-ons for some of the lower tiers of LogicMonitor service, but that's not something that we use with our agreement."
"In terms of pricing, I would rate LogicMonitor four out of five."
"It's an enterprise-grade solution and competitively priced compared to the other solutions that are out there... Our organization is not huge, but LogicMonitor is worth every penny that we pay for it. I've never heard anyone say, "I'm not sure that we're getting good value for money from this product." It's integral to our business."
"We pay for the enterprise tech support."
"The licensing side of things with LogicMonitor, is quite simple. It is one license per device. Recently, you have additional licenses with things, like LM Cloud, which does confuse things a bit. Because it's very hard to estimate how many licenses you're going to need until you're monitoring it, so it's quite hard through that process to give a customer price to say, "This is how much this services will cost.""
"We've had customers who have reduced their costs by not having multiple platforms for monitoring. That said, especially with super-large environments, the cost model for LogicMonitor is the one area where we run into issues."
"If you add more people, then you have to pay more, which is always a thing with the SaaS solutions."
"Licensing costs are around $700 a month, and the only additional costs, are phone costs in some instances."
"The cost is quite high. But if you want to get a full-featured application and you have a big team..."
"The solution is paid on a monthly basis and represents about 1% of the platform's budget."
"The cost is based on the package you select."
"PagerDuty has monthly and yearly licenses available, the costs of which can get quite high if you have a large number of users."
"The pricing may be about $1,000 per user."
"They're very good in pricing compared to the competitors in the area. I would rate them a five out of five in terms of pricing."
report
Use our free recommendation engine to learn which AIOps solutions are best for your needs.
814,649 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
22%
Financial Services Firm
11%
Manufacturing Company
9%
Healthcare Company
8%
Computer Software Company
21%
Financial Services Firm
13%
Manufacturing Company
7%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What is the best network monitoring software for large enterprises?
It actually depends on the exact purpose or requirements. Some tools are better for only network devices while others are better from a cloud monitoring or APM monitoring perspective. You can check...
What do you like most about LogicMonitor?
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 ...
What is your experience regarding pricing and costs for LogicMonitor?
The pricing can vary yearly or monthly, depending on the clients we're working with and their size and scale. For example, the pricing for a customer with ten thousand licenses versus a hundred lic...
What do you like most about PagerDuty?
The product easily integrates with other solutions.
What is your experience regarding pricing and costs for PagerDuty?
The price is very high. I rate the pricing a six out of ten. The license for stakeholders is very limited.
What needs improvement with PagerDuty?
It is difficult to send underlying trace files or statuses using PagerDuty. You can set up email alerts, but you cannot build any triggers using those email alerts. There are limitations; you canno...
 

Overview

 

Sample Customers

Kayak, Zendesk, Ted Baker, Trulia, Sophos, iVision, TekLinks, Siemens
40% of the Fortune 100 TrustPagerDuty. Customers include: Slack, Intuit, Zendesk, Panasonic, Pinterest, Airbnb, eHarmony, McKesson, Comcast
Find out what your peers are saying about LogicMonitor vs. PagerDuty Operations Cloud and other solutions. Updated: October 2024.
814,649 professionals have used our research since 2012.