No more typing reviews! Try our Samantha, our new voice AI agent.

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
25th
Average Rating
8.4
Reviews Sentiment
7.3
Number of Reviews
9
Ranking in other categories
Network Monitoring Software (15th), Server Monitoring (11th), Cloud Monitoring Software (19th)
Loom Systems
Ranking in IT Infrastructure Monitoring
61st
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (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 Loom Systems is 0.5%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring Mindshare Distribution
ProductMindshare (%)
Checkmk2.6%
Loom Systems0.5%
Other96.9%
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.
Keerthi Kumar Sangaraju - PeerSpot reviewer
Technology Manager at a tech services company with 10,001+ employees
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

"We can monitor multiple sites using the product."
"It's versatile, scalable, and easier to use compared to other solutions like Nagios and OMD."
"Checkmk was built on a platform that was user-friendly, and I could build my charts easily."
"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."
"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."
"Overall, from one to ten, I rate Checkmk a nine."
"The solution is absolutely scalable."
"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."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring and that it's a flexible solution."
"Bringing Loom in ensures that the incident process, request process, change, all of these processes are improved."
"The RFS portion of the solution is the product's most valuable feature."
"You can develop your own apps within Loom, and they can be configured very simply."
"The solution is very scalable; a company wouldn't have any issues expanding it if they needed to, and we have a few thousand users on the solution."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
 

Cons

"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 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."
"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."
"Checkmk does not allow running scripts at varying intervals."
"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."
"I think that the integration and the exporting of the data collected are areas where Checkmk lacks but should try to improve the most."
"It is easy for tech-savvy people, but newcomers might find it intimidating."
"The change management within the solution needs to be improved. There needs to be more process automation."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy, especially in the initial setup which can take six months of work, especially when you have a large estate that you're dealing with."
"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 reporting is a bit weak."
"The reporting is a bit weak. They should work to improve this aspect of the product."
"The change management within the solution needs to be improved. There needs to be more process automation."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"What's lacking in Loom Systems is the level of priority for each incident."
 

Pricing and Cost Advice

"Checkmk is a fairly reasonably priced solution."
"The product is affordable."
"The price of Checkmk is cheaper compared to other enterprise products."
Information not available
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
885,311 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%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise3
Large Enterprise2
No data available
 

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.
Ask a question
Earn 20 points
 

Comparisons

 

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 2026.
885,311 professionals have used our research since 2012.