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

Checkmk vs LogicMonitor comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 2024

Review summaries and opinions

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

Categories and Ranking

Checkmk
Ranking in Network Monitoring Software
15th
Ranking in IT Infrastructure Monitoring
27th
Ranking in Cloud Monitoring Software
19th
Average Rating
8.4
Reviews Sentiment
7.3
Number of Reviews
9
Ranking in other categories
Server Monitoring (11th)
LogicMonitor
Ranking in Network Monitoring Software
6th
Ranking in IT Infrastructure Monitoring
8th
Ranking in Cloud Monitoring Software
7th
Average Rating
9.0
Reviews Sentiment
7.1
Number of Reviews
34
Ranking in other categories
Application Performance Monitoring (APM) and Observability (13th), Container Monitoring (4th), AIOps (5th)
 

Mindshare comparison

As of February 2026, in the IT Infrastructure Monitoring category, the mindshare of Checkmk is 2.8%, down from 3.3% compared to the previous year. The mindshare of LogicMonitor is 2.5%, up from 2.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring Market Share Distribution
ProductMarket Share (%)
LogicMonitor2.5%
Checkmk2.8%
Other94.7%
IT Infrastructure Monitoring
 

Featured Reviews

reviewer1704309 - PeerSpot reviewer
IT Administrator at a construction company with 201-500 employees
Utilizing data monitoring capabilities and scripting potential to optimize system management
I frequently program functions with PowerShell, and although Bash could be used, my specialization is in PowerShell. Two of us focus on programming in PowerShell for infrastructure optimization. I set up a dedicated server to run scripts every hour, generating files for Checkmk output. However, Checkmk does not allow running scripts at varying intervals. I am working on this in the raw version of Checkmk.
Anshuman Thakur - PeerSpot reviewer
Site Reliability Engineer at a comms service provider with 501-1,000 employees
Monitoring has reduced downtime and now enables proactive alerts across cloud workloads
When it comes to the improvement of LogicMonitor, I think there are a few points that can be improved. The first one is alert tuning, which takes time. It requires effort when trying to understand it for the first time. The defaults do not always match our workload patterns, so I have to adjust the thresholds to reduce noise and avoid alert fatigue. While the dashboards are solid, I sometimes wish that the UI was a bit more intuitive when drilling down quickly during an incident. There are many options and finding the exact view where I can identify the exact problem takes a few extra clicks. When an alert comes and I click on a LogicMonitor alert, it takes time to understand what the alert actually is and to go through the data points. The alert page specifically could be better. The alert tuning part can also be made more simple. The first area that could be better is alert clarity and routing. Sometimes alerts do not include enough immediate context, so I still have to spend a few minutes correlating data across views. Adding more actionable details directly in the alert would make the response even faster. LogicMonitor sometimes gives false alerts as well. For example, if an EC2 instance is down, it will not determine whether the EC2 instance has been deliberately turned off or if it is actually not responding. At that time, it will give false alerts. The clearing of alerts is also an issue. Once an issue is fixed, the alert should be cleared, but it takes a little time for that alert to be cleared. Another improvement that would be helpful is simpler customization for complex dashboards. It is powerful, but building highly tailored dashboards, especially across multiple environments, can feel heavy and time-consuming. I would also appreciate a stronger out-of-the-box AWS correlation, such as automatically grouping related issues across EC2, EBS, and ALBs in a way that reads as a single incident story. This would reduce the mental overhead during outages. Grouping incidents together, such as all the EC2 alerts, all the EBS alerts, or all the load balancer alerts would be beneficial. Overall, none of these are blockers, just some improving areas. There could be smarter anomaly detection out of the box that can catch unusual but important behavior without manual tuning of every threshold. Better tagging and dynamic grouping for EC2 instances would also be helpful. Cleaner alert de-duplication so a single underlying issue does not generate multiple redundant alerts would improve the system. More guided root cause workflows would be beneficial, such as providing the most likely causes based on correlated metrics. Faster search navigation across devices, dashboards, and alerts during incidents would also improve the platform.

Quotes from Members

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

Pros

"I really like the auto-discovery feature."
"The alerting system in Checkmk really works properly."
"The initial setup of Checkmk was easy...It is a very stable solution."
"Checkmk helps me compare data and foresee issues."
"The most valuable features of Checkmk are its resource monitoring, infra monitoring, and log factor configuration."
"Overall, from one to ten, I rate Checkmk a nine."
"It's versatile, scalable, and easier to use compared to other solutions like Nagios and OMD."
"We can monitor multiple sites using the product."
"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."
"It is a really solid tool for the on-premises, physical and virtual infrastructure; I have had nothing but good things to say about it, and it has been a pleasure using it for those use cases."
"LogicMonitor has actually helped reduce our downtimes, helping us reduce downtime to about 40 to 50% by warning us before servers get heavy on usage or CPU load so we can take action in advance."
"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 initial setup is very simple."
"LogicMonitor has positively impacted our organization by especially improving service reliability and user experience, and the dynamic alerting and root cause analysis have helped us fix issues before they cause a full-blown outage or degrade performance for end users."
"LogicMonitor has positively impacted our organization by allowing us to implement it for 1,200 clients or 1,200 endpoints within three months, which went very well."
"The most valuable feature of LogicMonitor is the infrastructure monitoring capability."
 

Cons

"In Checkmk, the documentation can probably be improved a bit more."
"It is easy for tech-savvy people, but newcomers might find it intimidating."
"I think that the integration and the exporting of the data collected are areas where Checkmk lacks but should try to improve the most."
"If an alert is generated for a specific pattern in the log, and if Checkmk catches that log, it will stay there even after the alert is resolved."
"The main challenge for us is that we're moving from Nagios to Checkmk, and we're still getting used to the new way of working."
"Checkmk does not allow running scripts at varying intervals."
"Sometimes we receive alerts, and it can become annoying when you acknowledge an alert. It is very clunky when you acknowledge the alert. The process is not very intuitive, and there are instances where it feels a bit cumbersome to acknowledge an alert."
"The initial setup is a bit complex."
"I'd like to see more automation in the tool, especially around remediation."
"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."
"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."
"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."
"Sometimes alerts do not include enough immediate context, so I still have to spend a few minutes correlating data across views."
"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."
"While dynamic alerting is great, the overall alerting system can be complex to configure."
"I researched the pricing of LogicMonitor, and it costs around ten dollars per device per month, which is somewhat expensive compared to other products."
 

Pricing and Cost Advice

"The product is affordable."
"The price of Checkmk is cheaper compared to other enterprise products."
"Checkmk is a fairly reasonably priced solution."
"It is pretty expensive, but we now need one less full-time engineer. With on-prem, we used to have one more engineer in our department. That engineer has now moved to another department. Our capacity is better with this product than the previous one. It is easy for us to manage the sites. You have to choose between the standard account and the premium account. With the premium account, you get a lot more than the standard one, and you can also buy some extra features. It is a good thing to look at them because you would probably want to buy them. You should take your time and negotiate the price. They are easy. Like all cloud providers, they are able to discuss the price and if necessary, change the price."
"The tool's pricing falls into the middle range."
"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."
"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 have definitely seen ROI with LogicMonitor. We used to provide 24/7 IT support for our users. We have since been able to change to operating just within normal business hours for IT support, and LogicMonitor was a large part of being able to accomplish that."
"It can handle scaling. It is like any other cloud service. There is a cost associated with scaling, so we currently don't monitor all of our environments. We monitor just the customer-facing production environments. It would be nice if we could monitor our dominant environments, but we will have to pay a lot more due to the scaling issue. So, there's a balance there between what we would like and what we are willing to pay for."
"The pricing can be a little aggressive. Right now, it's a bit much for smaller organizations to adopt it. But comparatively, it also provides good features."
"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."
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
881,707 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Government
9%
Computer Software Company
9%
Manufacturing Company
9%
Comms Service Provider
8%
Manufacturing Company
11%
Financial Services Firm
10%
Computer Software Company
10%
Healthcare Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise3
Large Enterprise2
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise11
Large Enterprise11
 

Questions from the Community

What needs improvement with Checkmk?
I will get more information about Checkmk when the proof of concept is done. It's going to be before the summer. There will be a report about the tool and a recommendation to use it. So far, it loo...
What is your primary use case for Checkmk?
Checkmk ( /products/checkmk-reviews ) is a monitoring tool, so that's what I will use it for. Right now, it's not in production, but it's in a proof of concept phase. It looks good, so probably, du...
What advice do you have for others considering Checkmk?
I would rate Checkmk an eight out of ten, not knowing the final report.
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?
I researched the pricing of LogicMonitor, and it costs around ten dollars per device per month, which is somewhat expensive compared to other products. Some monitoring tools such as Zabbix are free...
 

Comparisons

 

Overview

 

Sample Customers

Information Not Available
Kayak, Zendesk, Ted Baker, Trulia, Sophos, iVision, TekLinks, Siemens
Find out what your peers are saying about Checkmk vs. LogicMonitor and other solutions. Updated: February 2026.
881,707 professionals have used our research since 2012.