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

Chronosphere vs Devo comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

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

Chronosphere
Ranking in Log Management
34th
Ranking in AIOps
22nd
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
3
Ranking in other categories
Application Performance Monitoring (APM) and Observability (36th)
Devo
Ranking in Log Management
21st
Ranking in AIOps
17th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
30
Ranking in other categories
Security Information and Event Management (SIEM) (16th), IT Operations Analytics (7th)
 

Mindshare comparison

As of November 2026, in the Log Management category, the mindshare of Chronosphere is 0.8%, up from 0.3% compared to the previous year. The mindshare of Devo is 1.4%, up from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management Mindshare Distribution
ProductMindshare (%)
Devo1.4%
Chronosphere0.8%
Other97.8%
Log Management
 

Featured Reviews

Karthik Doreswamy - PeerSpot reviewer
Dev Ops Engineer at a tech services company with 11-50 employees
Centralized monitoring has unified alerts and dashboards for critical cloud applications
We can improve a bit of UI aspects. The UI could be made more user friendly. Sometimes when identifying the specific logs patterns and identifying what metrics and what logs are coming in, going to a specific log explorer and finding it there is a little difficult. It would be very useful if we could group according to projects and have that UI a little more user friendly. The user interface part was a bit confusing in the beginning. To make it better, I believe we would need some more open sourced or freely available courses on Chronosphere which would help us understand the platform a bit more. The team provides detailed walkthroughs whenever you get into that. However, it would be better if we could have proper video sessions or documentation which would help us understand the tool a bit more.
Usama Khan - PeerSpot reviewer
Team Lead Soc at a tech services company with 51-200 employees
Advanced threat hunting has improved SOC visibility and now supports faster incident response
Devo can improve in how its connectors enhance integration with third-party tools. Devo's architecture works by having you deploy a relay server in the data center of the client side and Devo SIEM is basically on the AWS cloud. There are specific ports which are enabled on the relay server, which are 514 and 13000, 13151, 152. However, when we talk about databases and custom integrations, there are not default ports in the relay server. No default ports are defined. For JDBC drivers, the port number is 1433, but it is not in the relay server. You have to add it manually. For Oracle RDBMS, the port is 1521, and it is also not there by default. I would appreciate more third-party integrations including Fortinet and others. Machine learning models can also be improved. Playbooks in the SOAR can also be improved. Regarding playbooks for automation, we utilize playbooks for automation in SOAR for automated IOC blocking on a firewall, on a web application firewall, on DNS security, etc. The only option for us to run the playbook is to schedule the job for it. However, if I want to manually run the playbook, there is no option for doing so. This needs improvement.

Quotes from Members

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

Pros

"Integrating Chronosphere was pretty much easy coming from an open source tool and it helped us to streamline our monitoring and alerting setup across our organization, which directly impacted on the streamlining of the process as well as reducing errors and also keeping our environment uptime to a greater extent by those alerts and quick responses."
"Chronosphere has impacted my organization positively as for starters, we brought down the cost drastically since we completely moved to Chronosphere."
"The alerting features are good"
"The querying and the log-retention capabilities are pretty powerful. Those provide some of the biggest value-add for us."
"Those 400 days of hot data mean that people can look for trends and at what happened in the past. And they can not only do so from a security point of view, but even for operational use cases. In the past, our operational norm was to keep live data for only 30 days. Our users were constantly asking us for at least 90 days, and we really couldn't even do that. That's one reason that having 400 days of live data is pretty huge. As our users start to use it and adopt this system, we expect people to be able to do those long-term analytics."
"The user experience [is] well thought out and the workflows are logical. The dashboards are intuitive and highly customizable."
"In traditional BI solutions, you need to wait a lot of time to have the ability to create visualizations with the data and to do searches. With this kind of platform, you have that information in real-time."
"When comparing Devo with Splunk and Carbon Black, I think Devo is the leader."
"Devo provides good value and, given the quality of the product, I would expect to pay more."
"More than anything, we have seen ROI in the amount of time saved during investigations."
"The real-time analytics of security-related data are super. There are a lot of data feeds going into it and it's very quick at pulling up and correlating the data and showing you what's going on in your infrastructure. It's fast. The way that their architecture and technology works, they've really focused on the speed of query results and making sure that we can do what we need to do quickly. Devo is pulling back information in a fast fashion, based on real-time events."
 

Cons

"Sometimes when identifying the specific logs patterns and identifying what metrics and what logs are coming in, going to a specific log explorer and finding it there is a little difficult."
"In logging, I would prefer if Chronosphere could do something in the way of a dictionary or a JSON lookup kind of logging, which would be much easier in terms of directly searching for a particular keyword rather than a string match."
"It's not easy for everyone."
"There is room for improvement in the ability to parse different log types. I would go as far as to say the product is deficient in its ability to parse multiple, different log types, including logs from major vendors that are supported by competitors. Additionally, the time that it takes to turn around a supported parser for customers and common log source types, which are generally accepted standards in the industry, is not acceptable. This has impacted customer onboarding and customer relationships for us on multiple fronts."
"The cost is a little higher compared to other tools such as DataDog or Elasticsearch, so they could work on reducing costs."
"The price is one problem with Devo."
"In terms of return on investment with Devo, I'd say it has been costly due to the need for support and the overtime required for issues experienced at the beginning of the project."
"Devo has a lot of cloud connectors, but they need to do a little bit of work there."
"I would like to have the ability to create more complex dashboards."
"One major area for improvement for Devo... is to provide more capabilities around pre-built monitoring. They're working on integrations with different types of systems, but that integration needs to go beyond just onboarding to the platform. It needs to include applications, out-of-the-box, that immediately help people to start monitoring their systems. Such applications would include dashboards and alerts, and then people could customize them for their own needs so that they aren't starting from a blank slate."
"I have not observed a return on investment with Devo in terms of fewer employees needed, money saved, or time saved."
 

Pricing and Cost Advice

Information not available
"I'm not involved in the financial aspect, but I think the licensing costs are similar to other solutions. If all the solutions have a similar cost, Devo provides more for the money."
"It's very competitive. That was also a primary draw for us. Some of the licensing models with solutions like Splunk and Sentinel were attractive upfront, but there were so many micro-charges and services we would've had to add on to make them what we wanted. We had to include things like SOAR and extended capabilities, whereas all those capabilities are completely included with the Devo platform. I haven't seen any additional fee."
"[Devo was] in the ballpark with at least a couple of the other front-runners that we were looking at. Devo is a good value and, given the quality of the product, I would expect to pay more."
"Pricing is based on the number of gigabytes of ingestion by volume, and it's on a 30-day average. If you go over one day, that's not a big deal as long as the average is what you expected it to be."
"I rate the pricing a four on a scale of one to ten, where one is cheap, and ten is expensive."
"Be cautious of metadata inclusion for log types in pricing, as there are some "gotchas" with that."
"We have an OEM agreement with Devo. It is very similar to the standard licensing agreement because we are charged in the same way as any other customer, e.g., we use the backroom."
"Our licensing fees are billed annually and per terabyte."
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
920,939 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
12%
Transportation Company
12%
Outsourcing Company
9%
Financial Services Firm
9%
Financial Services Firm
16%
Outsourcing Company
11%
Construction Company
10%
Manufacturing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise6
Large Enterprise15
 

Questions from the Community

What needs improvement with Chronosphere?
In logging, I would prefer if Chronosphere could do something in the way of a dictionary or a JSON lookup kind of logging, which would be much easier in terms of directly searching for a particular...
What is your primary use case for Chronosphere?
My main use case for Chronosphere is logging, metrics, traceability, and raising alerts. A specific example of how I use Chronosphere for logging metrics or raising alerts is that we had a free int...
What advice do you have for others considering Chronosphere?
My advice to others looking into using Chronosphere is to go ahead for it. I gave Chronosphere a rating of 8 out of 10.
What needs improvement with Devo?
In terms of improvements, I think Devo falls short with their support model, as they rely mainly on their support team in Spain. Although they do have a support team in North America, they lack kno...
What is your primary use case for Devo?
Devo is the bank's centralized log management platform that my team and I rely on the most. For centralized log management in our day-to-day work, one of the biggest data users would be our Red Hat...
 

Comparisons

 

Overview

 

Sample Customers

Information Not Available
United States Air Force, Rubrik, SentinelOne, Critical Start, NHL, Panda Security, Telefonica, CaixaBank, OpenText, IGT, OneMain Financial, SurveyMonkey, FanDuel, H&R Block, Ulta Beauty, Manulife, Moneylion, Chime Bank, Magna International, American Express Global Business Travel
Find out what your peers are saying about Chronosphere vs. Devo and other solutions. Updated: October 2026.
920,939 professionals have used our research since 2012.