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

Logz.io vs Mezmo comparison

Why PeerSpot?
 

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

Logz.io
Ranking in Log Management
28th
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
10
Ranking in other categories
Security Information and Event Management (SIEM) (33rd)
Mezmo
Ranking in Log Management
55th
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Application Performance Monitoring (APM) and Observability (77th), Observability Pipeline Software (8th)
 

Mindshare comparison

As of October 2026, in the Log Management category, the mindshare of Logz.io is 1.2%, up from 0.6% compared to the previous year. The mindshare of Mezmo is 0.9%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management Mindshare Distribution
ProductMindshare (%)
Logz.io1.2%
Mezmo0.9%
Other97.9%
Log Management
 

Featured Reviews

Arkajyoti Misra - PeerSpot reviewer
Associate Director at Husk Power Systems
AI-driven observability has reduced investigation time and now improves uptime and customer trust
As for improvements needed in Logz.io, I think cost or pricing is always a consideration, especially since I come from a startup and an Indian company, making us look for products that provide better value for money. Compared to the market, their pricing appears decent but might need reevaluation as we scale further to remain competitive. The main concern for me is pricing, as feature-wise, I believe Logz.io is on par with other tools available in the market; however, it is not as widely discussed. Their features align with offerings from Elastic Stack and other prominent tools, including functionalities available from Prometheus or Grafana, providing centralized logging and other capabilities in the UI, so while the product direction is solid, improved pricing would immensely benefit us. I believe we have covered almost everything regarding improvements needed for Logz.io.
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

"The other nice thing about Logz.io is their team. When it comes to onboarding, their support is incredibly proactive. They bring the brand experience from a customer services perspective because their team is always there to help you refine filters and tweak dashboards. That is really a useful thing to have. Their engagement is really supportive."
"It is massively useful and great for testing. We can just go, find logs, and attach them easily. It has a very quick lookup. Whereas, before we would have to go, dig around, and find the server that the logs were connected to, then go to the server, download the log, and attach it. Now, we can just go straight to this solution, type in the log ID and server ID, and obtain the information that we want."
"The query mechanism for response codes and application health is valuable."
"The visualizations in Kibana are the most valuable feature; it's much more convenient to have a visualization of logs, and we can see status really clearly and very fast with just a couple of clicks."
"I can't imagine how I ever worked without it before."
"Our team doesn't spend time setting up, managing, and tuning a logging platform, which frees them up to spend time on higher value pieces of work and allows our people to focus on the high-value business change work."
"InsightOne is the main reason why we use LogMeIn. This is mostly because of log data that we are pushing tools and logs in general."
"Customer satisfaction scores before were around 60%, and now it has increased to over 75%; additionally, the uptime we had was below 99%, and now it stands at more than 99.5%, indicating we are performing much better."
"LogDNA consolidates all logs into one place, which is super valuable."
"The solution aggregates all event streams, so that if there are any issues, it's all in the same interface."
"We haven't had anything yet that we couldn't do through LogDNA."
"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."
 

Cons

"The product needs improvement from a filtering perspective."
"However, at this lower scale, we feel it does not deliver the expected value for the money we are paying, reiterating my concern about cost."
"I would like granularity on alerting so we can get tentative alerts and major alerts, then break it down between the two, but they do have a lot of good alerting stuff in there already."
"Capacity planning could be a little bit of a struggle."
"The solution needs to improve its data retention. It should be greater than seven days. The product needs to improve its documentation as well."
"I would like them to improve how they manage releases. Some of our integrations integrate specifically with set versions. Logz.io occasionally releases an update that might break that integration. On one occasion, we found out a little bit too late, then we had to roll it back."
"When it comes to reducing our troubleshooting time, it depends. When there are no bugs in Logz.io, it reduces troubleshooting by 5 to 10 percent. When there are bugs, it increases our troubleshooting time by 200 percent or more."
"The solution needs to expand its access control and make it accessible through API."
"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."
"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."
"No ability to encapsulate a query or a filter, and communicate or share that among the team."
 

Pricing and Cost Advice

"You pay for what you need, and that is a good model. They are also quite happy to talk to you about your uses and your use case. They will even go as far as suggesting things that you don't need to do in order to save you money. At one point, I was quite surprised at how cheap it could be if we wanted it to be or how much they would help us manage our costs."
"At the time it was set up, we thought Logz.io was very reasonable for what we were getting in terms of how much time and hosting costs it was saving us, because you don't have to run the servers for it anymore."
"The product's pricing is cheaper than other solutions."
"The product is a little expensive."
"The tool is an open source product."
Information not available
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
915,287 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
16%
Financial Services Firm
11%
Construction Company
10%
Manufacturing Company
10%
Comms Service Provider
18%
Construction Company
14%
Transportation Company
14%
Financial Services Firm
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise2
Large Enterprise7
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Logz.io?
Organizations that start with clear logging standards and retention policies can integrate applications, cloud resources, and Kubernetes workloads early to maximize the observability benefits. They...
What needs improvement with Logz.io?
Logz.io can be improved by adding more AI-assisted root cause analysis and by improving log retention flexibility. They can also provide additional dashboard customization options. Logz.io is a ver...
What is your primary use case for Logz.io?
We have been using Logz.io for more than one year. Our main use case for Logz.io is centralized log management and observability. We collect logs from multiple applications and infrastructure compo...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

Logz
LogDNA
 

Overview

 

Sample Customers

Dish Network, The Economist, Forbes, Holler, Kenshoo, OneSpan, Siemens, Sisense, Unity, ZipRecruiter
Instacart, Asics, Lime, Salesforce
Find out what your peers are saying about Logz.io vs. Mezmo and other solutions. Updated: September 2026.
915,287 professionals have used our research since 2012.