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

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
11th
Ranking in Log Management
16th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
29
Ranking in other categories
IT Infrastructure Monitoring (15th), Container Monitoring (6th), Cloud Monitoring Software (11th)
Mezmo
Ranking in Application Performance Monitoring (APM) and Observability
75th
Ranking in Log Management
56th
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Observability Pipeline Software (8th)
 

Mindshare comparison

As of June 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Elastic Observability is 1.8%, down from 5.2% compared to the previous year. The mindshare of Mezmo is 0.5%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Mindshare Distribution
ProductMindshare (%)
Elastic Observability1.8%
Mezmo0.5%
Other97.7%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Mohammed-Abdelalim - PeerSpot reviewer
Assistant Vice President at QualityKiosk Technologies Pvt. Ltd.
Has provided powerful customization for unique monitoring needs but needs more out-of-the-box capabilities
In my opinion, the best features of Elastic Observability are their flexibility to integrate with other existing systems and the ability to build a unified monitoring tool that can integrate with existing ones and end-to-end user journeys which require a lot of customizations. The greatest feature in Elastic is the ability to customize. This is similar to my comments about customizable dashboards in Elastic because it's visible to the analyst. However, it's very great. Customizing these dashboards can meet the customer's specific use cases and specific stories that they have in their environment, their special environment that doesn't look like other environments. The dashboarding in Elastic is highly customizable to the level of logos. If the customer wants his company logo in the dashboard, it can be done.
TO
President and Founder at STILLWATER SUPERCOMPUTING INC
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

"In addition to the fact that we are more proactive in the detection of incident before they occur, we can on one click see the request path from the customer to the backend."
"I think Elastic Observability is already in very good shape."
"We can view and connect different sources to the dashboard using it."
"Machine learning is the most valuable feature of this solution."
"We use AppDynamics and Elastic. The reason why we're using Elastic APM is because of the license count. It's very favorable compared to AppDynamics. It's inexpensive; it's economical."
"Good design and easy to use once implemented."
"I have built a mini business intelligence system based on Elastic Observability."
"The product has connectors to many services."
"With LogDNA, which brings all the logs together in an interleaved stream, it allows us to take a transaction and relate it to other contextual events making the gathering of evidence for auditors and our internal RCA much more productive."
"We haven't had anything yet that we couldn't do through LogDNA."
"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

"If we had some pre-defined templates for observability that we could start using right away after deploying it – instead of having to build or to change some of the dashboards – that would be helpful."
"More web features could be added to the product."
"There's a steep learning curve if you've never used this solution before."
"The only challenging aspect for new users is often writing the query language."
"The solution would be better if it was capable of more automation, especially in a monitoring capacity or for the response to abnormalities."
"The price is the only issue in the solution. It can be made better and cheaper."
"Simplifying the parsing of logs and manual efforts would also be beneficial."
"Elastic Observability could improve asset discovery as the current requirement to push the agent is not ideal."
"Scalability could be improved; we are using it through the IBM cloud deployment and on some of the data centers that are very heavily used, there is a significant lag in the event stream, sometimes 10, 15 minutes behind, which makes the RCA impossible."
"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

"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."
"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."
"Since we are a huge company, Elastic Observability is an affordable solution for us."
"The price of Elastic Observability is expensive."
"The product is not that cheap."
"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."
Information not available
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
11%
Government
7%
Manufacturing Company
7%
Transportation Company
18%
Construction Company
16%
Comms Service Provider
11%
Financial Services Firm
9%
 

Company Size

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

Questions from the Community

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?
After careful consideration about areas for improvement in Elastic Observability, aspects such as pricing, customization, implementation, and scalability could be improved. As a user of the system,...
What is your primary use case for Elastic Observability?
My use case for Elastic Observability is observability, as we upload our customers' data, including logs, and when there is an issue, we can analyze what went wrong.
Ask a question
Earn 20 points
 

Comparisons

 

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: June 2026.
900,644 professionals have used our research since 2012.