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

Elastic Observability vs Stackify 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

Elastic Observability
Ranking in Application Performance Monitoring (APM) and Observability
11th
Ranking in IT Infrastructure Monitoring
15th
Ranking in Log Management
15th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
29
Ranking in other categories
Container Monitoring (5th), Cloud Monitoring Software (11th)
Stackify
Ranking in Application Performance Monitoring (APM) and Observability
63rd
Ranking in IT Infrastructure Monitoring
66th
Ranking in Log Management
58th
Average Rating
7.8
Number of Reviews
6
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Elastic Observability is 1.9%, down from 5.4% 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.
Application Performance Monitoring (APM) and Observability Mindshare Distribution
ProductMindshare (%)
Elastic Observability1.9%
Stackify0.7%
Other97.4%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

Mohammed-Abdelalim - PeerSpot reviewer
Assistant Vice President at QualityKiosk Technologies Pvt. Ltd.
Has provided powerful customization for unique monitoring needs but needs more out-of-the-box capabilities
In my opinion, the best features of Elastic Observability are their flexibility to integrate with other existing systems and the ability to build a unified monitoring tool that can integrate with existing ones and end-to-end user journeys which require a lot of customizations. The greatest feature in Elastic is the ability to customize. This is similar to my comments about customizable dashboards in Elastic because it's visible to the analyst. However, it's very great. Customizing these dashboards can meet the customer's specific use cases and specific stories that they have in their environment, their special environment that doesn't look like other environments. The dashboarding in Elastic is highly customizable to the level of logos. If the customer wants his company logo in the dashboard, it can be done.
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

"In addition to the fact that we are more proactive in the detection of incident before they occur, we can on one click see the request path from the customer to the backend."
"The solution allows us to dig deep into data."
"It has always been a stable solution."
"The architecture and system's stability are simple."
"The Elastic User Interface framework lets us do custom development when needed. You need to have some Javascript knowledge. We need that knowledge to develop new custom tests."
"It is a powerful tool that allows users to collect and transform logs as needed, enabling flexible visualization and analysis."
"I recommend Elastic Observability for its completeness of vision and wide ecosystem."
"Elastic Observability significantly improves incident response time by providing quick access to logs and data across various sources. For instance, searching for specific keywords in logs spanning over a month from multiple data sources can be completed within seconds."
"It is very simple and very easy to configure."
"The solution is stable and reliable."
"The deployment is very fast."
"We switched from New Relic and Loggly as it provides us more info at a lower price."
"The performance dashboard and the accurate level of details are beneficial."
"What stood out to us were the metrics and granular details we received."
"The solution is stable and reliable."
"Within few hours of install we've identify the source of issue we've been investigating for few days and couldn't pin point."
 

Cons

"The solution needs to use more AI. Once the product onboards AI, users would more effectively be able to track endpoints for specific messages."
"The price is the only issue in the solution. It can be made better and cheaper."
"There's a steep learning curve if you've never used this solution before."
"The auto-discovery isn't nearly as good. When you drop the agent onto the JVM and you're trying to figure things out, having to go through and manually do all that is cumbersome."
"They need more skills in the market. There are not enough skills in the market."
"Simplifying the parsing of logs and manual efforts would also be beneficial."
"I would have preferred built-in tools to manage the indexes on deployment for better visual representation, as the initial feedback regarding system performance and data storage was fairly primitive and lacking."
"Elastic Observability could improve asset discovery as the current requirement to push the agent is not ideal."
"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."
"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."
"Better mobile support."
"The search feature could be improved."
"It should be easily scalable and configurable in different instances."
"Another improvement would be the agent memory utilization, which led to our recent reevaluation."
"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."
 

Pricing and Cost Advice

"Pricing is one of those situations where the more you use it, the more you pay."
"The product is not that cheap."
"We will buy a premium license after POC."
"The product’s pricing needs improvement."
"Elastic Observability is cheaper than other similar solutions, such as Dynatrace. Its license calculation is based on various factors like data volume and physical infrastructure, particularly related to RAM capacity."
"Since we are a huge company, Elastic Observability is an affordable solution for us."
"The price of Elastic Observability is expensive."
"There are two types: cloud and SaaS. They charge based on data ingestion, ingest rate, hard retention, and warm retention. I believe it costs around $25,000 annually to ingest 30GB of data daily. That is the SaaS version. There is also a self-managed license where the customer manages their own infrastructure on-prem. In such cases, there are three license tiers that respectively cost $5,000 annually per node, $7,000 per node, and $12,500 per node."
"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.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
11%
Government
7%
Manufacturing Company
7%
Construction Company
19%
Comms Service Provider
14%
Media Company
9%
Performing Arts
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise16
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise2
 

Questions from the Community

What is your experience regarding pricing and costs for Elastic Observability?
The problem is their licensing model, which is a bit confusing. Many customers struggle to understand their total cost of ownership because Elastic licensing is not dependent on easy, quantifiable ...
What needs improvement with Elastic Observability?
After careful consideration about areas for improvement in Elastic Observability, aspects such as pricing, customization, implementation, and scalability could be improved. As a user of the system,...
What is your primary use case for Elastic Observability?
My use case for Elastic Observability is observability, as we upload our customers' data, including logs, and when there is an issue, we can analyze what went wrong.
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

PSCU, Entel, VITAS, Mimecast, Barrett Steel, Butterfield Bank
MyRacePass, ClearSale, Newitts, Carbonite, Boston Software, Children's International, Starkwood Media Group, Fewzion
Find out what your peers are saying about Elastic Observability vs. Stackify and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.