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

Mezmo vs Stackify 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

Mezmo
Ranking in Application Performance Monitoring (APM) and Observability
76th
Ranking in Log Management
54th
Average Rating
9.0
Number of Reviews
2
Ranking in other categories
Observability Pipeline Software (5th)
Stackify
Ranking in Application Performance Monitoring (APM) and Observability
62nd
Ranking in Log Management
63rd
Average Rating
7.8
Number of Reviews
6
Ranking in other categories
IT Infrastructure Monitoring (57th)
 

Mindshare comparison

As of April 2025, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Mezmo is 0.1%, up from 0.1% compared to the previous year. The mindshare of Stackify is 0.2%, down from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

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."
Moses Arigbede - PeerSpot reviewer
Easy to set up with great custom dashboards but needs to improve non-.NET infrastructure
They need to improve non-.NET infrastructure. We always had difficulty when it comes to reporting or metrics that come from Linux operating systems and Docker containers. For anything that runs within the Unix environment, we always had problems with them, however, if it was a document-based application, Stackify was 100%, it gave everything. Now, the aggregation agent, the metric agent for Stackify for Linux, collects everything. When I say everything, I mean, everything. It collects so much information that we now started to term it as useless data as all that ingestion will just come in and overwhelm your log retention limit for the month and really this spike up your cost at the end of the month. You'll need to do a lot in order to train down the data coming in from all your Linux environments, to get to what you really need, which actually takes some time as well. I would like to be able to see metrics about individual running containers on the host machines. Stackify has not really gotten that right, as far as I'm concerned. Netdata has done a better job and New Relic has also done a better job. They need to improve on that. We need to be able to see the individual resource usage of containers running within a particular host.

Quotes from Members

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

Pros

"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."
"The filter feature on Stackify is one of the features I found valuable. It's awesome. When I want to get the application logs, the solution gives me many filters. For example, if I want to get logs from my test environment, the option is there for me to select the environment from Stackify, and you can also select the particular application, and you'll see the information you need there. The filter feature alone and the fact that Stackify offers a lot of different filters is what I like the most about the solution because I've used other tools with the filter feature, but the filtering was very difficult, versus Stackify that has good filtering. On Stackify, you can filter the information by the last one hour, or the last four hours, and you can also select the date range and specify the timestamp, then the solution will give you the information based on the date range you specified. Another feature I found valuable on Stackify is its rating feature because it tells you how your application is faring. For example, a rating of A means excellent, while a rating of F means very bad, or that your application is not doing well at all. The ratings are from A to F. I also like that Stackify helps you in terms of load management because the solution gives you information on overutilized resources. These are the most valuable features of the solution."
"The solution is stable and reliable."
"The deployment is very fast."
"The performance dashboard and the accurate level of details are beneficial."
 

Cons

"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."
"I've not used Stackify for a while, and I'm currently using a solution now that's not as good as Stackify. Among the solutions I've been using so far, Stackify has been one of the best for me, but there's always room for improvement. For example, I don't know if it's just me, but when I try to get the log from Stackify, sometimes it doesn't appear in real-time. It takes a few minutes before the logs appear. When I redeploy my solution and the application starts, I don't see the logs immediately, and it would take two to three minutes before I see the logs. I don't know if other customers have a similar experience. It's the wait time for the logs to appear that's a concern for me, could be improved, and is what the Stackify team should be looking into. In terms of any additional feature that I'd like added to the solution, I'm not sure if Stackify has a way to export logs out. I've been trying to do it. On the solution, you can click on a spiral-like icon and it shows you the entire error, and I'd prefer an export button that would let me download the error and save that into a text file, for example, so it'll be available on my local machine for me to reference it, especially because the log keeps going and as you're using the solution, the system keeps pushing messages on to Stackify, so if I'm looking at a particular error at 12:05 PM, for example, by the time I go back to my system and would like to revisit the error at 12:25 PM, on Stackify, the logs would have gone past that level and I won't see it again which makes it difficult. When you now go back to that timestamp, you don't tend to see it immediately, but if the solution had an export feature for me to save that particular error information on my local machine for reference at a later time, I won't have to go back to Stackify. I just go to that log, specifically to that particular export that I've received on my local machine. I can get it and review it, and it would be easier that way versus me going back to Stackify to find that particular error and request that particular information."
"I would like to be able to see metrics about individual running containers on the host machines."
"It should be easily scalable and configurable in different instances."
"The search feature could be improved."
 

Pricing and Cost Advice

Information not available
"The price is variable. It depends on how much data we have received in that particular month. Usually, it goes up to $2,000, or, at times, $3,000 USD per month."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
848,253 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
20%
Computer Software Company
15%
Manufacturing Company
7%
Insurance Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Comparisons

 

Also Known As

LogDNA
No data available
 

Overview

 

Sample Customers

Instacart, Asics, Lime, Salesforce
MyRacePass, ClearSale, Newitts, Carbonite, Boston Software, Children's International, Starkwood Media Group, Fewzion
Find out what your peers are saying about Mezmo vs. Stackify and other solutions. Updated: April 2025.
848,253 professionals have used our research since 2012.