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

CrowdStrike Observability [EOL] vs Elastic Observability comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Aug 26, 2026

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

CrowdStrike Observability [...
Average Rating
8.0
Reviews Sentiment
4.9
Number of Reviews
8
Ranking in other categories
No ranking in other categories
Elastic Observability
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
29
Ranking in other categories
Application Performance Monitoring (APM) and Observability (10th), IT Infrastructure Monitoring (13th), Log Management (14th), Container Monitoring (6th), Cloud Monitoring Software (11th)
 

Featured Reviews

HectorRios - PeerSpot reviewer
IT COMMUNICATIONS AND NETWORKS at Américas BPS
Has provided reliable alerts and helped identify infrastructure issues through detailed reporting
The best features of CrowdStrike Observability include the way they show issues to the client or agent, and their data collection method is interesting because they use an agent-less approach in some cases, collecting data from infrastructure such as firewalls. Additionally, they have the agent, but the presentation in the management console is excellent as we have observability end-to-end with the servers and all the services configured in the use cases. The intelligent alerting feature is excellent and configured on our console, being highly effective as it detects real alerts and just warnings or real issues. Identifying performance bottlenecks is important because they collect numerous MD5 or hash keys including movements or playbooks. The way they organize that in the console is excellent, allowing you to have reports detecting issues, which not only includes detection but also provides solutions to those issues.
Stefan Decuypere - PeerSpot reviewer
Technology Consultant at Hybrid software
Real-time dashboards and visual insights have streamlined issue analysis and monitoring
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, I know what it costs but am not directly involved in cost-benefit evaluations or maintenance, which is handled by another team. I develop the visual representation of the data and frankly, I don't see major gaps in my application or anything I would really miss; I appreciate the fast pace of the developments that have occurred in the last couple of years. Regarding room for improvement in Elastic Observability, 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.

Quotes from Members

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

Pros

"In the logs and the trajectory, it shows detailed information about where the source of infection comes from, how it travels, and how to reach there."
"CrowdStrike Observability is a signature-less solution where you don't need to update your endpoints or the CrowdStrike Observability agents regularly, and it is completely based on AI and ML search engines."
"I find the most effective feature of CrowdStrike Observability to be its cloud vision and attack surface vision, which enhance network traffic analysis."
"The dashboard and user interface of CrowdStrike Observability are quite good, and the support is responsive."
"The log aggregation and correlation of data are notable features that enhance our operations."
"The intelligence database provided by CrowdStrike is very impressive."
"The intelligent alerting feature is excellent and configured on our console, being highly effective as it detects real alerts and just warnings or real issues."
"The best features of CrowdStrike Observability include the way they show issues to the client or agent, and their data collection method is interesting because they use an agent-less approach in some cases, collecting data from infrastructure such as firewalls."
"The architecture and system's stability are simple."
"All the features that we use, such as monitoring, dashboarding, reporting, the possibility of alerting, and the way we index the data, are important."
"From my experience with several major customers, the most valued feature of Elastic is its log analytics capabilities."
"Machine learning is the most valuable feature of this solution."
"I think Elastic Observability is already in very good shape."
"We can view and connect different sources to the dashboard using it."
"It's easy to deploy, and it's very flexible."
"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."
 

Cons

"We had some difficulties at the beginning, but at this moment they are improving, so probably in some months I will give them a ten."
"The areas of CrowdStrike Observability that have room for improvement include the approach towards customer issues, where resolution takes time."
"For reporting or log management, having a longer duration for backup without needing to purchase a paid subscription would be beneficial. Currently, there is a default ninety-day backup period."
"Technical support received a rating of 4 out of 10."
"Integration with Huawei should be more straightforward."
"The customer service is not satisfactory for me. The support is only available in English, and my users in LATAM regions such as Peru and Colombia require local language support, which is not currently provided."
"From the different deployments I have worked with, the shortcomings of CrowdStrike Observability are often because of what clients are able to share with CrowdStrike."
"The pricing is very high and small companies cannot afford it. They should reduce the price because the backend infrastructure is the same."
"There could be more low-code features included in the product."
"When I go to the portal, I do not see many insights on the endpoints or where there could be latencies."
"The tool's scalability involves a more complex implementation process. It requires careful calculations to determine the number of nodes needed, the specifications of each node, and the configuration of hot, warm, and cold zones for data storage. Additionally, managing log retention policies adds further complexity. The solution's pricing also needs to be cheaper."
"I am familiar with Azure Monitor, which I find more user-friendly compared to Elastic, which is a very technical tool."
"Elastic Observability’s price could be improved."
"It lacked some capabilities when handling on-prem devices, like network observability, package flow analysis, and device performance data on the infrastructure side."
"I would advise others to use a different solution than Elastic APM."
"The only challenging aspect for new users is often writing the query language."
 

Pricing and Cost Advice

Information not available
"The product’s pricing needs improvement."
"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."
"Users have to pay for some features, like the alerts on different channels, because they are unavailable in different source versions."
"We have been using the open-source version."
"Since we are a huge company, Elastic Observability is an affordable solution for us."
"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."
"We will buy a premium license after POC."
"Pricing is one of those situations where the more you use it, the more you pay."
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
913,630 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Construction Company
13%
Financial Services Firm
11%
Comms Service Provider
8%
Financial Services Firm
14%
Computer Software Company
9%
Comms Service Provider
7%
Manufacturing Company
7%
 

Company Size

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

Questions from the Community

What needs improvement with CrowdStrike Observability?
From the different deployments I have worked with, the shortcomings of CrowdStrike Observability are often because of what clients are able to share with CrowdStrike. If there are limitations in wh...
What is your primary use case for CrowdStrike Observability?
We are currently using a complete suite of anti-malware software and other security products in our company. I have worked with both the on-premises version and the cloud version, but I am more fam...
What advice do you have for others considering CrowdStrike Observability?
I am probably familiar with CrowdStrike Observability. I first heard of CrowdStrike Observability a couple of years ago, and I only really started looking into it about a year ago. I cannot comment...
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.
 

Overview

 

Sample Customers

Information Not Available
PSCU, Entel, VITAS, Mimecast, Barrett Steel, Butterfield Bank
Find out what your peers are saying about Splunk, Wazuh, Datadog and others in Log Management. Updated: September 2026.
913,630 professionals have used our research since 2012.