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

Elastic Observability vs LogRhythm SIEM 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:
 

ROI

Sentiment score
6.3
Elastic Observability enhances efficiency, reduces incidents, and provides cost-effective visibility, with benefits in data management and availability.
Sentiment score
5.7
LogRhythm SIEM enhances detection, response times, productivity, and security posture, offering cost-effectiveness and resource savings for medium-sized organizations.
 

Customer Service

Sentiment score
7.5
Elastic Observability users praise responsive, knowledgeable support, valuing quick problem-solving, though rely on documentation for added assistance.
Sentiment score
5.4
LogRhythm SIEM's support excels in expertise and quick resolutions, earning high satisfaction despite occasional delays.
Elastic support really struggles in complex situations to resolve issues.
The technical support is good; we have a separate portal for partners, and since we are paying for the service, they provide a response timeframe based on severity—critical issues are addressed within four hours, medium issues within one day, and non-urgent issues may take a couple of days.
Customer support is very helpful and effectively solves my problems.
 

Scalability Issues

Sentiment score
7.1
Elastic Observability offers scalable performance and ease of use, with user satisfaction varying based on specific implementations and preferences.
Sentiment score
7.8
LogRhythm SIEM is highly scalable, easily expands across environments, and integrates well, suitable for medium to large enterprises.
Elastic Observability seems to have a good scale-out capability.
Elastic Observability is easy in deployment in general for small scale, but when you deploy it at a really large scale, the complexity comes with the customizations.
What is not scalable for us is not on Elastic's side.
LogRhythm SIEM is highly scalable as it has modular components allowing me to expand storage, indexing, or other resources as needed.
LogRhythm SIEM is scalable; it can handle about 200 or 500 devices without much difference.
The scalability of LogRhythm SIEM is good enough, warranting an eight out of ten rating.
 

Stability Issues

Sentiment score
8.1
Elastic Observability is stable, efficiently handles analytics, and is well-regarded by users, though monitoring storage is recommended.
Sentiment score
4.7
LogRhythm SIEM is stable with high uptime, strong support, handling large data, though updates may affect stability.
There are some bugs that come with each release, but they are keen always to build major versions and minor versions on time, including the CVE vulnerabilities to fix it.
It is very stable, and I would rate it ten out of ten based on my interaction with it.
Elastic Observability is really stable.
The platform needs regular updates to fix problems encountered with each quarterly patch and version release.
LogRhythm SIEM still needs improvement regarding stability, particularly in environments with heavy data consumption.
 

Room For Improvement

Elastic Observability needs improved automation, ease of use, dashboard customization, advanced metrics, compatibility, and streamlined deployment processes.
LogRhythm SIEM needs improved integration, user interface, automation, scalability, documentation, and compatibility with non-mainstream platforms and Linux.
For instance, if you have many error logs and want to create a rule with a custom query, such as triggering an alert for five errors in the last hour, all you need to do is open the AI bot, type this question, and it generates an Elastic query for you to use in your alert rules.
It lacked some capabilities when handling on-prem devices, like network observability, package flow analysis, and device performance data on the infrastructure side.
Some areas such as AI Ops still require data scientists to understand machine learning and AI, and it doesn't have a quick win with no-brainer use cases.
I have noticed some problems with parsing errors, event mismatches, and data mismatching, so ensuring accurate parsing and continuous improvement according to device updates are my basic expectations as a detection engineer.
There is currently no way to determine how much data is being consumed in terms of gigabytes, terabytes, or petabytes from particular devices or environments.
A more user-friendly user interface with drag-and-drop features, similar to key competitors like Splunk, would be beneficial.
 

Setup Cost

Elastic Observability offers cost-effective, flexible pricing for enterprises, though high-tier licensing may be expensive for smaller users.
LogRhythm SIEM is cost-effective for enterprises, offering transparent pricing and flexible licensing, yet incurs higher professional service fees.
The license is reasonably priced, however, the VMs where we host the solution are extremely expensive, making the overall cost in the public cloud high.
Elastic Observability is cost-efficient and provides all features in the enterprise license without asset-based licensing.
Observability is actually cheaper compared to logs because you're not indexing huge blobs of text and trying to parse those.
The license cost is around $10 per MPS.
I find LogRhythm SIEM affordable, as it is a bit less costly than QRadar.
 

Valuable Features

Elastic Observability enhances incident response with powerful search, centralized logging, machine learning, and scalable integration for seamless monitoring and alerting.
LogRhythm SIEM offers advanced threat detection, user-friendly interface, comprehensive log management, and automated alerts for enhanced security efficiency.
The most valuable feature is the integrated platform that allows customers to start from observability and expand into other areas like security, EDR solutions, etc.
the most valued feature of Elastic is its log analytics capabilities.
All the features that we use, such as monitoring, dashboarding, reporting, the possibility of alerting, and the way we index the data, are important.
The seamless integration for case management, along with a user-friendly dashboard user interface, makes tasks like threat hunting more efficient.
We have enough budget for cloud deployment, but we choose to keep it on-prem to ensure data privacy; cyberattacks are a concern, but data privacy is the foremost priority due to sensitive government information.
This helps SOC analysts significantly as they can monitor all log sources through a dashboard, quickly identifying which sources haven't reported within their specified timeframes.
 

Categories and Ranking

Elastic Observability
Ranking in Log Management
14th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
28
Ranking in other categories
Application Performance Monitoring (APM) and Observability (7th), IT Infrastructure Monitoring (10th), Container Monitoring (4th), Cloud Monitoring Software (6th)
LogRhythm SIEM
Ranking in Log Management
13th
Average Rating
8.4
Reviews Sentiment
6.4
Number of Reviews
175
Ranking in other categories
Security Information and Event Management (SIEM) (8th)
 

Mindshare comparison

As of October 2025, in the Log Management category, the mindshare of Elastic Observability is 1.3%, down from 1.9% compared to the previous year. The mindshare of LogRhythm SIEM is 2.3%, down from 2.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management Market Share Distribution
ProductMarket Share (%)
LogRhythm SIEM2.3%
Elastic Observability1.3%
Other96.4%
Log Management
 

Featured Reviews

Adelina Craciun - PeerSpot reviewer
Customization enables tailored monitoring and alerting across departments
The possibility to customize it has been quite useful. Whatever the other departments want to dream up, we implement. Whatever they want to monitor, the granularity of it, the changes in the threshold, and the anomalies that they want reported all require some development. So far, every single request has been fulfilled.
SumitKumar20 - PeerSpot reviewer
Tool consistently aids in effective threat detection and monitoring but could benefit from improved log source management and resource optimization
One major area for improvement in LogRhythm SIEM is the lack of volume measurement capability in terms of storage. There is currently no way to determine how much data is being consumed in terms of gigabytes, terabytes, or petabytes from particular devices or environments. This information is crucial for planning future storage needs and scalability. The system monitor (collector) agent has issues with resource consumption. Even when not actively collecting data, the agent continues to consume significant CPU and memory resources, which can be particularly problematic for small business environments with limited resources. LogRhythm SIEM could improve by adding more default device support. While they have good default settings for devices such as Palo Alto firewalls, custom log sources often require extensive work. Increasing the number of supported devices with built-in policies and functionality would reduce the need for custom work. Competitive SIEM tools often provide more comprehensive coverage for various devices and vendors.
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
869,760 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Computer Software Company
14%
Manufacturing Company
8%
Government
6%
Computer Software Company
12%
Government
10%
Manufacturing Company
8%
Financial Services Firm
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise4
Large Enterprise16
By reviewers
Company SizeCount
Small Business38
Midsize Enterprise38
Large Enterprise83
 

Questions from the Community

What do you like most about Elastic Observability?
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...
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?
Out-of-the-box use cases have room for improvement in Elastic Observability. They don't invest a lot in building out-of-the-box observable use cases, and they are more focusing on giving a very fle...
What is the difference between log management and SIEM?
Rony, Daniel's answer is right on the money. There are many solutions for each in the market, a lot depends upon your ability to manage such tools and your budget. A small operation may be best s...
What needs improvement with LogRhythm NextGen SIEM?
One major area for improvement in LogRhythm SIEM is the lack of volume measurement capability in terms of storage. There is currently no way to determine how much data is being consumed in terms of...
What do you like most about LogRhythm SIEM?
I find LogRhythm's log management capabilities to be beneficial.
 

Also Known As

No data available
LogRhythm NextGen SIEM, LogRhythm, LogRhythm Threat Lifecycle Management, LogRhythm TLM
 

Overview

 

Sample Customers

PSCU, Entel, VITAS, Mimecast, Barrett Steel, Butterfield Bank
Macy's, NASA, Fujitsu, US Air Force, EY, Abbott, HD Supply, SAB Miller, UCLA, Raytheon, Amtrak, Cargill
Find out what your peers are saying about Elastic Observability vs. LogRhythm SIEM and other solutions. Updated: September 2025.
869,760 professionals have used our research since 2012.