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
25th
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 March 2026, in the IT Infrastructure Monitoring category, the mindshare of Checkmk is 2.6%, down from 3.6% compared to the previous year. The mindshare of LogicMonitor is 2.8%, up from 2.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring Mindshare Distribution
ProductMindshare (%)
LogicMonitor2.8%
Checkmk2.6%
Other94.6%
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

"Overall, from one to ten, I rate Checkmk a nine."
"The most valuable feature of the solution is that it has a lot of different pieces, and they all work together...It is a very scalable solution. Scalability-wise, I rate the solution a ten out of ten."
"Checkmk was built on a platform that was user-friendly, and I could build my charts easily."
"The alerting system in Checkmk really works properly."
"The initial setup of Checkmk was easy...It is a very stable solution."
"I really like the auto-discovery feature."
"Checkmk helps me compare data and foresee issues."
"It's versatile, scalable, and easier to use compared to other solutions like Nagios and OMD."
"We have very fine-tuned alerting that lets us know when there are issues by identifying where exactly that issue is, so we can troubleshoot and resolve them quickly. This is hopefully before the customer even notices. Then, it gives us some insight into potential issues coming down the road through our environmental health 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 dashboards are the big seller for us. When our customers can see those graphs and are able to interact with the data, that is valuable. They can easily adjust time ranges and the graphs display the data fast. We've used other tools in the past, where you'd say, "Hey, I want the last three months of data on a graph," and it would just sit there and crunch for five minutes before you'd actually see the data. With LogicMonitor, the fast reliability of those dashboards is huge."
"It has had a solid impact and has helped us to resolve issues faster with everything in real time and the alerts."
"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."
"LogicMonitor has positively impacted my organization by being up to date with all the latest features and capabilities, so as our organization develops cutting-edge systems, whether internal or third party, we can always rely on LogicMonitor to provide proper enterprise level monitoring and observability."
"LogicMonitor has positively impacted our organization by cutting down white noise and false positives, allowing our team to be more proactive than reactive, which cuts down on the SLOs and SLAs we are trying to meet at all times."
"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."
 

Cons

"In Checkmk, the documentation can probably be improved a bit more."
"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."
"I think that the integration and the exporting of the data collected are areas where Checkmk lacks but should try to improve the most."
"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."
"The initial setup is a bit complex."
"It is easy for tech-savvy people, but newcomers might find it intimidating."
"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."
"Checkmk does not work too easily with the PowerStore. I use a PowerShell script as Checkmk runs on Linux and a Windows system, connecting with the Checkmk agent."
"The container monitoring seems to be really behind compared to some bespoke cloud-native monitoring solutions that are designed around Kubernetes, containers, and ephemeral environments."
"The ease of use with data source tuning could be improved. That can get hairy quickly. When I reach out for help, it's usually around a data source or event source configuration. That can get challenging."
"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 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."
"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."
"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."
"While dynamic alerting is great, the overall alerting system can be complex to configure."
 

Pricing and Cost Advice

"The price of Checkmk is cheaper compared to other enterprise products."
"Checkmk is a fairly reasonably priced solution."
"The product is affordable."
"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.""
"In terms of pricing, I would rate LogicMonitor four out of five."
"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 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."
"We are on an enterprise license plan, we are paying $7.75 per device a month. That is for a commitment of 350 devices. Anything that is over the 350 is charged at 1.2 times the rate; 1.2 times $7.75 would be the overage charge. We are looking at increasing our commitment to either 450 or 500 devices. It changes our pricing if we go to 450 devices, bringing it from $7.75 down to $7.70. If we go for 500 devices, it brings it from $7.75 down to $7.50. We will probably factor in the volume discount drop from $7.75 to $7.50 in our decision of whether we uplift or not. We also have some cloud monitors, which are about $500 a month."
"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."
"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."
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
884,797 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Government
9%
Manufacturing Company
9%
Computer Software Company
9%
Comms Service Provider
8%
Manufacturing Company
11%
Computer Software Company
10%
Financial Services Firm
9%
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: March 2026.
884,797 professionals have used our research since 2012.