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

Elastic Observability vs Mezmo 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

Elastic Observability
Ranking in Application Performance Monitoring (APM) and Observability
7th
Ranking in Log Management
14th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
28
Ranking in other categories
IT Infrastructure Monitoring (10th), Container Monitoring (4th), Cloud Monitoring Software (6th)
Mezmo
Ranking in Application Performance Monitoring (APM) and Observability
75th
Ranking in Log Management
50th
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Observability Pipeline Software (7th)
 

Mindshare comparison

As of October 2025, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Elastic Observability is 3.9%, down from 6.5% compared to the previous year. The mindshare of Mezmo is 0.3%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Market Share Distribution
ProductMarket Share (%)
Elastic Observability3.9%
Mezmo0.3%
Other95.8%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Adelina Craciun - PeerSpot reviewer
Customization enables tailored monitoring and alerting across departments
The possibility to customize it has been quite useful. Whatever the other departments want to dream up, we implement. Whatever they want to monitor, the granularity of it, the changes in the threshold, and the anomalies that they want reported all require some development. So far, every single request has been fulfilled.
TO
It consolidates all logs into one place and provides required features and functionalities
Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to do RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue.

Quotes from Members

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

Pros

"I recommend Elastic Observability for its completeness of vision and wide ecosystem."
"Machine learning is the most valuable feature of this solution."
"Elastic APM has plenty of features, such as the Elastic server for Kibana and many additional plugins. It's a comprehensive tool when used as a logging platform."
"The tool's most valuable feature is centralized logging. Elastic Common Search helps us to search for the logs across the organization."
"Its diverse set of features available on the cloud is of significant importance."
"Elastic provides built-in features for queries and report generation. It's a very good tool for monitoring integration capabilities."
"Good design and easy to use once implemented."
"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 over a month from multiple data sources can be completed within seconds."
"The solution aggregates all event streams, so that if there are any issues, it's all in the same interface."
"LogDNA consolidates all logs into one place, which is super valuable."
 

Cons

"There could be more low-code features included in the product."
"There is room for improvement regarding its APM capabilities."
"I am familiar with Azure Monitor, which I find more user-friendly compared to Elastic, which is a very technical tool."
"The interface could be improved."
"There's a steep learning curve if you've never used this solution before."
"The cost must be made more transparent."
"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 is reactive rather than proactive. It should act as an ITSM tool and be able to create tickets and alerts on Jira."
"Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue."
"No ability to encapsulate a query or a filter, and communicate or share that among the team."
 

Pricing and Cost Advice

"The price of Elastic Observability is expensive."
"The product’s pricing needs improvement."
"Elastic Observability's pricing could be better for small-scale users."
"Users have to pay for some features, like the alerts on different channels, because they are unavailable in different source versions."
"One needs to pay for the licenses, and it is an annual subscription model right now."
"Pricing is one of those situations where the more you use it, the more you pay."
"Elastic Observability is cheaper than other similar solutions, such as Dynatrace. Its license calculation is based on various factors like data volume and physical infrastructure, particularly related to RAM capacity."
"We have been using the open-source version."
Information not available
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
869,566 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Computer Software Company
14%
Manufacturing Company
8%
Government
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise4
Large Enterprise16
No data available
 

Questions from the Community

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 is your experience regarding pricing and costs for Elastic Observability?
The problem is their licensing model, which is a bit confusing. Many customers struggle to understand their total cost of ownership because Elastic licensing is not dependent on easy, quantifiable ...
What needs improvement with Elastic Observability?
Out-of-the-box use cases have room for improvement in Elastic Observability. They don't invest a lot in building out-of-the-box observable use cases, and they are more focusing on giving a very fle...
Ask a question
Earn 20 points
 

Also Known As

No data available
LogDNA
 

Overview

 

Sample Customers

PSCU, Entel, VITAS, Mimecast, Barrett Steel, Butterfield Bank
Instacart, Asics, Lime, Salesforce
Find out what your peers are saying about Elastic Observability vs. Mezmo and other solutions. Updated: September 2025.
869,566 professionals have used our research since 2012.