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
33rd
Average Rating
9.0
Reviews Sentiment
6.5
Number of Reviews
3
Ranking in other categories
No ranking in other categories
Mezmo
Ranking in Log Management
54th
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Application Performance Monitoring (APM) and Observability (76th), Observability Pipeline Software (5th)
 

Mindshare comparison

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

Featured Reviews

Mustafa Husny - PeerSpot reviewer
Helps to collect logs from various data sources, including hardware
I use Logstash primarily for connecting logs from hardware. This is the main use case. The second use case involves making correlations between logs from various sources.  I can collect logs from various data sources, including hardware. The product needs to improve its compatibility.  I rate…
TO
Has vastly increased our ability to reach SLA targets consistently
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. If an event hits but you don't have the information to look at it, then it's tricky. This is probably not an issue of the product itself, but more a deployment issue. There is something on the IBM side that needs some readjustment to make certain these lags don't happen too often. We now use other tools for back-up in that area. But if you really want to do SIEM type work, then that is an aspect that needs some improvement. It's hard to tell if it's the product or the IBM deployment of it. The user interface is really very productive interactively but for an additional feature, it would be nice if we somehow could encapsulate a query or a filter, and communicate or share that among the team so that specific types of actions can be carried out quickly. In particular, when we deal with a customer issue, it may pertain to a particular transaction through the system and each transaction has a unique ID. It would be great if we could query that ID and request all transactions that pertain to a specific ID. For now, we need to find the events, then extract the ID. Once we have that, we can go through the UI to set up the query and filter it to give us a transaction. But it would be really nice if we could simply say, "Here's the ID. Give me all the transactions."

Quotes from Members

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

Pros

"I can collect logs from various data sources, including hardware."
"Logstash has numerous plugins for inputs and outputs, allowing it to work well in environments that do not contain other Elastic components."
"We have three or four Logstash servers for high availability."
"Everything aligns well with improving our organization."
"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."
 

Cons

"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."
"Elastic does not provide proper support for Logstash worldwide, and I rate their technical support as one out of ten."
"The product needs to improve its compatibility."
"No ability to encapsulate a query or a filter, and communicate or share that among the team."
"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."
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
847,625 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
13%
Government
9%
Educational Organization
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?
Logstash lacks a graphical user interface, necessitating a strong programming background to handle it effectively. It is challenging for business users who need a skilled team for its operation. Ch...
What is your primary use case for Logstash?
I am considered an expert in Elastic Observability ( /products/elastic-observability-reviews ) in the Middle East. During my experience, I have worked heavily on Logstash ( /products/logstash-38586...
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: April 2025.
847,625 professionals have used our research since 2012.