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

Checkmk vs Loom Systems 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 IT Infrastructure Monitoring
13th
Average Rating
8.4
Reviews Sentiment
7.3
Number of Reviews
9
Ranking in other categories
Network Monitoring Software (11th), Server Monitoring (5th), Cloud Monitoring Software (12th)
Loom Systems
Ranking in IT Infrastructure Monitoring
64th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (2nd)
 

Mindshare comparison

As of April 2025, in the IT Infrastructure Monitoring category, the mindshare of Checkmk is 3.9%, up from 2.4% compared to the previous year. The mindshare of Loom Systems is 0.2%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring
 

Featured Reviews

Paolo Sala - PeerSpot reviewer
A reasonably priced tool for system and application monitoring
The main room for improvement is in the solution's presentation and the integration area. In our company, we use the integration capabilities from ServiceNow. We also have another big monitoring solution in place in our company, which is Dynatrace. At the moment, there doesn't exist an out-of-the-box integration for Dynatrace. 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 only implementation of Checkmk that allows high availability is the virtual appliance that has the option for the availability of a different box. Otherwise, you have to find a way to implement it manually with some custom solution, which could be an improvement.
Keerthi Kumar Sangaraju - PeerSpot reviewer
Stable, easy to set up, flexible, and has multiple functionalities, but needs to define priority levels for each incident
What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority.

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."
"Checkmk was built on a platform that was user-friendly, and I could build my charts easily."
"Checkmk helps me compare data and foresee issues."
"We can monitor multiple sites using the product."
"The most valuable features of Checkmk are its resource monitoring, infra monitoring, and log factor configuration."
"The initial setup of Checkmk was easy...It is a very stable solution."
"I really like the auto-discovery feature."
"It's versatile, scalable, and easier to use compared to other solutions like Nagios and OMD."
"You can develop your own apps within Loom, and they can be configured very simply."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring. I also like that it's a flexible solution."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
"The RFS portion of the solution is the product's most valuable feature."
 

Cons

"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."
"In Checkmk, the documentation can probably be improved a bit more."
"The initial setup is a bit complex."
"I think that the integration and the exporting of the data collected are areas where Checkmk lacks but should try to improve the most."
"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."
"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."
"What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"The change management within the solution needs to be improved. There needs to be more process automation."
"The reporting is a bit weak. They should work to improve this aspect of the product."
 

Pricing and Cost Advice

"Checkmk is a fairly reasonably priced solution."
"The price of Checkmk is cheaper compared to other enterprise products."
"The product is affordable."
Information not available
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
847,625 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Financial Services Firm
9%
Manufacturing Company
8%
Government
8%
Financial Services Firm
22%
Computer Software Company
22%
Real Estate/Law Firm
10%
Construction Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Checkmk?
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.
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...
Ask a question
Earn 20 points
 

Comparisons

No data available
 

Overview

 

Sample Customers

Information Not Available
Citrix, Amdocs, Sysaid, Hexaware, Effibar, Revtrak, Taptica
Find out what your peers are saying about Checkmk vs. Loom Systems and other solutions. Updated: March 2025.
847,625 professionals have used our research since 2012.