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

Stackify vs Sumo Logic Observability comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jul 24, 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

Stackify
Ranking in Application Performance Monitoring (APM) and Observability
62nd
Average Rating
7.8
Number of Reviews
6
Ranking in other categories
IT Infrastructure Monitoring (57th), Log Management (63rd)
Sumo Logic Observability
Ranking in Application Performance Monitoring (APM) and Observability
20th
Average Rating
7.8
Reviews Sentiment
7.2
Number of Reviews
6
Ranking in other categories
Cloud Monitoring Software (21st), AIOps (10th)
 

Mindshare comparison

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

Featured Reviews

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.
Shamshir Nangla - PeerSpot reviewer
Getting up and running is easy, even for a newbie but management of searches definitely needs improvement
Operational effectiveness with regards to when there's an issue, when there's a reactive issue, people are able to, or as well as proactively, actually, because we use their PagerDuty integrations. We use queries in Sumo Logic to trigger alerts based on logging. That allows us to proactively identify issues as they're happening. With those same alerts, obviously, with that platform, you can use it to reactively start looking at troubleshooting issues as they're happening right then and there or incidents. So it's been very, very good for alerting and for troubleshooting issues. For predicting issues before they happen, it is not very good. They have a feature called anomaly detection, but I think it's quite premature compared to other stuff out there. So it's good for alerts and for troubleshooting operational effectiveness. When your operations are down or segregated, it's perfect because it will help you diagnose the issues.

Quotes from Members

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

Pros

"The performance dashboard and the accurate level of details are beneficial."
"The solution is stable and reliable."
"The deployment is very fast."
"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."
"We use queries in Sumo Logic to trigger alerts based on logging. That allows us to proactively identify issues as they're happening."
"The product is easy to learn."
"Sumo Logic Observability presents a range of valuable features, including well-crafted dashboards and a diverse selection of helpful apps. However, personally, I don't hold a favorable opinion of the solution. While I don't struggle with writing queries, my main difficulty lies in recruiting competent individuals and ensuring their proficiency in utilizing the solution. This often leads to additional challenges and complexities. From my perspective, when compared to Microsoft Sentinel or even Splunk, Sumo Logic Observability has a steeper learning curve. One contributing factor to this disparity is the solution's long existence in the market compared to Synlogic. Nevertheless, I acknowledge that there are capable and knowledgeable professionals employed at Sumo Logic Observability. The effectiveness of the solution largely depends on how it is integrated into your internal operations and environment. Its utility and benefits can vary significantly. It is worth noting that organizations like the NSA and, I believe, the CIA used it in the past, primarily for rapidly searching and analyzing large volumes of data. To leverage its capabilities effectively, you must determine how to tailor it to your specific needs."
"Alerting and consistency are key. We have different tiers with log collectors, and continuous querying provides near-real-time updates. It's almost like instantly when something happens, like pending transactions or error fees. This helps reduce incident resolution time compared to waiting for thresholds on other platforms. We can continue logging in with them seamlessly and quickly get into action."
"I have not seen any stability issues in the product."
"The solution allows multiple groups to converge on a unified platform, allowing for different utilization by various teams."
 

Cons

"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."
"The search feature could be improved."
"It should be easily scalable and configurable in different instances."
"Fine-grained data can be quite frustrating to work with and should be made easier."
"Implementing a more streamlined enrichment process, and conceptualizing the observability data collection as an ETL pipeline would be helpful."
"Documentation could be better. While it's generally good, sometimes finding what you need requires extensive searching. It's not always clear where to look for specific things."
"The speed of queries could be improved. When using more advanced functions, especially with large datasets like the 90-day log retention we had, queries could be slow, sometimes taking up to five minutes."
"SearchUI.exe is a bit clunky in the product, making it an area where the product needs improvements."
 

Pricing and Cost Advice

"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."
"Now, they’re not charging by ingests anymore. You should expect the price to be a bit of an unknown and to basically increase as the business increases."
"I started on the free tier to try it out, but because of our usage, we're now paying for it."
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
Financial Services Firm
20%
Computer Software Company
15%
Manufacturing Company
7%
Insurance Company
6%
Financial Services Firm
16%
Computer Software Company
14%
Manufacturing Company
10%
Transportation Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
What needs improvement with Sumo Logic Observability?
The speed of queries could be improved. When using more advanced functions, especially with large datasets like the 90-day log retention we had, queries could be slow, sometimes taking up to five m...
What is your primary use case for Sumo Logic Observability?
We used it for log observability – log aggregation specifically.
 

Overview

 

Sample Customers

MyRacePass, ClearSale, Newitts, Carbonite, Boston Software, Children's International, Starkwood Media Group, Fewzion
Information Not Available
Find out what your peers are saying about Stackify vs. Sumo Logic Observability and other solutions. Updated: April 2025.
848,253 professionals have used our research since 2012.