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

Logz.io 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

Logz.io
Ranking in Log Management
32nd
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
9
Ranking in other categories
Security Information and Event Management (SIEM) (38th)
Stackify
Ranking in Log Management
58th
Average Rating
7.8
Number of Reviews
6
Ranking in other categories
Application Performance Monitoring (APM) and Observability (62nd), IT Infrastructure Monitoring (68th)
 

Mindshare comparison

As of August 2026, in the Log Management category, the mindshare of Logz.io is 1.2%, up from 0.5% compared to the previous year. The mindshare of Stackify is 0.7%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management Mindshare Distribution
ProductMindshare (%)
Logz.io1.2%
Stackify0.7%
Other98.1%
Log Management
 

Featured Reviews

Udit Parekh - PeerSpot reviewer
DevOps Engineer at Veefin
Centralized logs have improved troubleshooting and now reduce production incident impact
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 very mature and grown platform with very good features. Most improvements should be around automation, AI-driven insights, and cost visibility. Because Logz.io is a very mature and grown platform that is very good, cost optimization can be made for higher costs related to higher log volumes. For larger organizations, custom dashboards can be improved. In terms of root cause analysis, there can be more AI-assisted root cause analysis capabilities.
IE
Senior Software Engineer at a tech services company with 1,001-5,000 employees
Has good filtering and rating features and helps with resource and load management
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.

Quotes from Members

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

Pros

"I can't imagine how I ever worked without it before."
"We use the product for log collection and monitoring."
"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."
"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."
"The query mechanism for response codes and application health is valuable."
"We use the tool to track the dev and production environment."
"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."
"It is very simple and very easy to configure."
"The deployment is very fast."
"The solution is stable and reliable."
"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."
"Within few hours of install we've identify the source of issue we've been investigating for few days and couldn't pin point."
"The performance dashboard and the accurate level of details are beneficial."
"What stood out to us were the metrics and granular details we received."
"My advice to anyone who wants to use Stackify is to go for it because my experience with it is good."
 

Cons

"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."
"The product needs improvement from a filtering perspective."
"The price can be cheaper and they should have better monitoring."
"The solution needs to expand its access control and make it accessible through API."
"The solution needs to improve its data retention. It should be greater than seven days. The product needs to improve its documentation as well."
"Capacity planning could be a little bit of a struggle."
"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."
"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."
"Better mobile support."
"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."
"Another improvement would be the agent memory utilization, which led to our recent reevaluation."
"I'm looking to see more performance tools, but heard that they are going to release some."
"It's not easy to set up. It's hard especially for juniors to understand."
"One thing that happens as a new user on Stackify is when you install the agent it pulls everything and if you're not careful, your log allowance will just be exhausted as you are actually pulling too much data."
"I would like to be able to see metrics about individual running containers on the host machines."
"The search feature could be improved."
 

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."
"The tool is an open source product."
"The product's pricing is cheaper than other solutions."
"The product is a little expensive."
"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 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 Log Management solutions are best for your needs.
909,153 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
13%
Financial Services Firm
11%
Construction Company
10%
Manufacturing Company
10%
Construction Company
21%
Comms Service Provider
13%
Outsourcing Company
9%
Media Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise1
Large Enterprise7
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise2
 

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
No data available
 

Overview

 

Sample Customers

Dish Network, The Economist, Forbes, Holler, Kenshoo, OneSpan, Siemens, Sisense, Unity, ZipRecruiter
MyRacePass, ClearSale, Newitts, Carbonite, Boston Software, Children's International, Starkwood Media Group, Fewzion
Find out what your peers are saying about Logz.io vs. Stackify and other solutions. Updated: August 2026.
909,153 professionals have used our research since 2012.