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

Logstash vs Mezmo comparison

 

Comparison Buyer's Guide

Executive Summary

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

Logstash
Ranking in Log Management
24th
Average Rating
9.0
Reviews Sentiment
5.6
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Mezmo
Ranking in Log Management
52nd
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Application Performance Monitoring (APM) and Observability (80th), Observability Pipeline Software (7th)
 

Mindshare comparison

As of August 2025, in the Log Management category, the mindshare of Logstash is 0.6%, up from 0.4% compared to the previous year. The mindshare of Mezmo is 0.2%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management
 

Featured Reviews

PRANIL CHANDARKAR - PeerSpot reviewer
Open-source accessibility and ease of implementation empower adaptable log management
As both a customer and an integrator, I think the best features in Logstash are that people prefer it because it is open to all, as it is an open-source version. The functionality of Logstash is quite easy to implement. I can say that the plugin ecosystem of Logstash is great. I have used some plugins for shell script monitoring and for SQL monitoring, and these are all working well with Logstash. The real-time processing capabilities of Logstash are also pretty fine with the tool. When I use the community edition, I have to do many things manually. If I am using enterprise Elastic, then that is taken care of by the Elastic native machine learning.
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

"Logstash has numerous plugins for inputs and outputs, allowing it to work well in environments that do not contain other Elastic components."
"I can collect logs from various data sources, including hardware."
"The transformation means we ship the logs in the way that we want them to be presented in Kibana, which is the main function we use Logstash for."
"Everything aligns well with improving our organization."
"We have three or four Logstash servers for high availability."
"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

"The product needs to improve its compatibility."
"Almost all the research can be very bad. We still have a problem with importing the log system."
"We still have a problem with importing the log system."
"There can be a UI to implement with Logstash. Currently, I have to work with config files and everything."
"Elastic does not provide proper support for Logstash worldwide, and I rate their technical support as one out of ten."
"An enhancement we could implement is the ability to cluster Logstash to exist in more than one node."
"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."
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
865,384 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
12%
Government
9%
University
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Questions from the Community

What do you like most about Logstash?
I can collect logs from various data sources, including hardware.
What needs improvement with Logstash?
Customization can be automated with Logstash, but it is at the developer's disposal. The developer has to do it, not the tool as such. There is scope for optimization, but that is all outside the t...
What is your primary use case for Logstash?
The purposes for which I am using Logstash largely include log aggregation and application monitoring.
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

No data available
LogDNA
 

Overview

 

Sample Customers

Information Not Available
Instacart, Asics, Lime, Salesforce
Find out what your peers are saying about Logstash vs. Mezmo and other solutions. Updated: July 2025.
865,384 professionals have used our research since 2012.