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

Checkmk vs Elastic Observability comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 2024
 

Categories and Ranking

Checkmk
Ranking in IT Infrastructure Monitoring
13th
Ranking in Cloud Monitoring Software
11th
Average Rating
8.4
Number of Reviews
7
Ranking in other categories
Network Monitoring Software (14th), Server Monitoring (6th)
Elastic Observability
Ranking in IT Infrastructure Monitoring
9th
Ranking in Cloud Monitoring Software
7th
Average Rating
7.8
Number of Reviews
24
Ranking in other categories
Application Performance Monitoring (APM) and Observability (8th), Log Management (13th), Container Monitoring (4th)
 

Mindshare comparison

As of November 2024, in the IT Infrastructure Monitoring category, the mindshare of Checkmk is 2.9%, up from 2.6% compared to the previous year. The mindshare of Elastic Observability is 4.3%, up from 3.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring
 

Featured Reviews

Paolo Sala - PeerSpot reviewer
Aug 24, 2023
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.
Subramani K - PeerSpot reviewer
Jun 27, 2022
The user interface framework lets us do custom development when needed.
So Elastic is basically clusters, right? Basically three, we can go with the basic cluster is a three note cluster. So the implementation is quite simple. It's not very complex. So we have to architect the solution in such a way that we have the right number of replicas and right number of charts and all those to hold the data. So basically we have to architect based on the data ingestion, how much data we are going to ingest in the cluster. So this setup is pretty simple, but we have to have the right inputs, right decisions in place before we even implement it.

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."
"I really like the auto-discovery feature."
"It's versatile, scalable, and easier to use compared to other solutions like Nagios and OMD."
"The most valuable features of Checkmk are its resource monitoring, infra monitoring, and log factor configuration."
"The alerting system in Checkmk really works properly."
"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 initial setup of Checkmk was easy...It is a very stable solution."
"It has always been a stable solution."
"The product has connectors to many services."
"Good design and easy to use once implemented."
"Its diverse set of features available on the cloud is of significant importance."
"The price is very less expensive compared to the other solutions."
"The most valuable feature of Elastic Observability is the text search."
"The ability to ensure that the data is searchable and maintainable is highly valuable for our purposes."
"We can view and connect different sources to the dashboard using it."
 

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."
"In Checkmk, the documentation can probably be improved a bit more."
"The initial setup is a bit complex."
"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."
"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."
"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."
"Elastic Observability is reactive rather than proactive. It should act as an ITSM tool and be able to create tickets and alerts on Jira."
"Elastic Observability is an excellent product for monitoring and visibility, but it lacks predictive analytics. Most solutions are aligned with the AIOps requirements, but this piece is missing in Elastic and should be included."
"The tool's scalability involves a more complex implementation process. It requires careful calculations to determine the number of nodes needed, the specifications of each node, and the configuration of hot, warm, and cold zones for data storage. Additionally, managing log retention policies adds further complexity. The solution's pricing also needs to be cheaper."
"Elastic Observability’s price could be improved."
"The solution needs to use more AI. Once the product onboards AI, users would more effectively be able to track endpoints for specific messages."
"Improving code insight related to infrastructure and network, particularly focusing on aspects such as firewalls, switches, routers, and testing would be beneficial."
"I am familiar with Azure Monitor, which I find more user-friendly compared to Elastic, which is a very technical tool."
"There could be more low-code features included in the product."
 

Pricing and Cost Advice

"The price of Checkmk is cheaper compared to other enterprise products."
"The product is affordable."
"Checkmk is a fairly reasonably priced solution."
"There are two types: cloud and SaaS. They charge based on data ingestion, ingest rate, hard retention, and warm retention. I believe it costs around $25,000 annually to ingest 30GB of data daily. That is the SaaS version. There is also a self-managed license where the customer manages their own infrastructure on-prem. In such cases, there are three license tiers that respectively cost $5,000 annually per node, $7,000 per node, and $12,500 per node."
"The price of Elastic Observability is expensive."
"We will buy a premium license after POC."
"The product is not that cheap."
"Since we are a huge company, Elastic Observability is an affordable solution for us."
"Pricing is one of those situations where the more you use it, the more you pay."
"One needs to pay for the licenses, and it is an annual subscription model right now."
"Elastic Observability's pricing could be better for small-scale users."
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
814,763 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Government
8%
Financial Services Firm
8%
Manufacturing Company
7%
Financial Services Firm
22%
Computer Software Company
15%
Manufacturing Company
9%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
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. But basically, we're okay with it. The difficult part was adapting fro...
What is your primary use case for Checkmk?
We use it to monitor mainly Linux servers, including operating system metrics, processes, services, and so on. We also use scripting and monitoring logs.
What do you like most about Elastic Observability?
Elastic Observability significantly improves incident response time by providing quick access to logs and data across various sources. For instance, searching for specific keywords in logs spanning...
What needs improvement with Elastic Observability?
I don't know how Elastic can improve. The integration feature I am using is very easy to implement.
 

Comparisons

 

Learn More

 

Overview

 

Sample Customers

Information Not Available
PSCU, Entel, VITAS, Mimecast, Barrett Steel, Butterfield Bank
Find out what your peers are saying about Checkmk vs. Elastic Observability and other solutions. Updated: October 2024.
814,763 professionals have used our research since 2012.