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

Elastic Observability vs InfoScale comparison

 

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

Elastic Observability
Ranking in IT Infrastructure Monitoring
13th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
29
Ranking in other categories
Application Performance Monitoring (APM) and Observability (11th), Log Management (16th), Container Monitoring (5th), Cloud Monitoring Software (11th)
InfoScale
Ranking in IT Infrastructure Monitoring
26th
Average Rating
8.6
Reviews Sentiment
6.1
Number of Reviews
9
Ranking in other categories
Data Loss Prevention (DLP) (19th), High Availability Clustering (1st), Disaster Recovery (DR) Software (14th), Data Storage for Kubernetes (2nd), Autonomous Operational Resilience (4th)
 

Mindshare comparison

As of August 2026, in the IT Infrastructure Monitoring category, the mindshare of Elastic Observability is 1.3%, down from 3.3% compared to the previous year. The mindshare of InfoScale is 0.0%. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring Mindshare Distribution
ProductMindshare (%)
Elastic Observability1.3%
InfoScale0.0%
Other98.7%
IT Infrastructure Monitoring
 

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.
TJ
Site Reliability Engineer (Certified) at Kyndryl India
Automated recovery has minimized downtime and supports seamless multi‑datacenter failover
Beyond pricing, there are areas where I would like to see InfoScale improved or enhanced. Veritas offers three management approaches. The first, which Veritas currently recommends, is Veritas Operation Manager. The second is the Cluster Manager Java Console graphical interface. The Cluster Manager Java Console has not been revised since version 6.1 or 6.2. This tool was critical for me, particularly valuable when managing small cluster footprints of 20 to 30 server nodes. I relied heavily on this tool, but Veritas has moved away from it in favor of Operation Manager. I recommend Veritas continue evolving this tool rather than discarding it. The third approach is the command line, suitable for individuals with extensive Veritas expertise and experience, but command line use in live environments consumed excessive time, leading me to prefer the graphical interface. Apart from pricing, I have not discovered disadvantages. The product is excellent. My concern is Veritas discarding the Cluster Manager Java Console in favor of Veritas Operation Manager. Setting up Operation Manager requires time and a dedicated server that runs continuously. I had to create a single server just for Veritas Operation Manager. While this works well for larger environments with hundreds of clusters, it is less useful for smaller deployments. I still recommend Veritas reconsider this application and evolve it by incorporating new features from Veritas Operation Manager. Adding these new features to the Java console would be beneficial because that tool runs on my laptop without consuming environment resources, and I can connect directly to clusters from my laptop. I am not opposing Veritas Operation Manager, which is excellent and resembles hardware management consoles for power machines, but smaller tools that previously performed these tasks should remain as options to provide clients with greater ease. From a features and functionality perspective, I do not find missing features in InfoScale at this moment. However, I am not actively using Veritas, managing only legacy machines on older hardware. I am upgrading operating systems but not Veritas due to contract expiration and end-of-life status. The contract is not being renewed because the customer wants to move away. Since I have not logged into VCS since 2021 and transferred responsibilities to another team, I am unaware of features arriving in version 8 or beyond and cannot comment specifically on recent Veritas introductions.

Quotes from Members

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

Pros

"All the features that we use, such as monitoring, dashboarding, reporting, the possibility of alerting, and the way we index the data, are important."
"Its diverse set of features available on the cloud is of significant importance."
"The very positive features are the cost effectiveness and the range of things that you can implement."
"It's easy to deploy, and it's very flexible."
"For full stack observability, Elastic is the best tool compared with any other tool like New Relic or AppDynamics or Dynatrace."
"The solution allows us to track performance via metrics and we're able to see where latency is happening."
"The customizable dashboards in Elastic Observability allow us to group relevant data to specific aspects of our solution, giving us around 20 interlinked dashboards which provide an overview, and if one aspect shows weird behavior, we can focus on that specific aspect of our software with a dedicated dashboard."
"The tool's most valuable feature is centralized logging. Elastic Common Search helps us to search for the logs across the organization."
"The best feature in InfoScale is the file system, which is the greatest feature as you can get any storage LUN from any hardware because it's software-defined and create a volume that can consist of storage from two or more different vendors, which avoids any vendor lock-in and makes it easier when you expand as time goes."
"Over the last two years, we did not experience any application failover or receive alerts due to the immediate switchover mechanism in active-active mode that ensures no downtime, helping us significantly with confidence and trust in our organization."
"InfoScale does that all by itself without any dependency on different solutions."
"In a live incident scenario, the data replication process occurs in real-time, and compared to other products, this data replication feature works effectively, ensuring data availability, and we can implement this scenario using Veritas Volume Replication (VVR), which is the most usable feature in InfoScale for data replication."
"InfoScale's ability to maintain data integrity and availability during a cyber event such as a ransomware attack is excellent."
"It's a stable solution."
"The best feature is that it supports high availability and automatic failover, which minimizes downtime and helps the environment reduce downtime and improve high availability for critical applications."
"From a recovery standpoint, InfoScale is excellent and easy to manage."
 

Cons

"When opening tickets, we cannot use our team mailbox."
"With Elastic, you need to code and program more things compared to Dynatrace."
"The auto-discovery isn't nearly as good. That's a big portion of it. 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."
"More web features could be added to the product."
"Elastic Observability needs to improve the retrieval of logs and metrics from all the instances."
"It lacked some capabilities when handling on-prem devices, like network observability, package flow analysis, and device performance data on the infrastructure side."
"Elastic Observability needs to have better standardization, logging, and schema."
"If we had some pre-defined templates for observability that we could start using right away after deploying it – instead of having to build or to change some of the dashboards – that would be helpful."
"Based on my experience with support, I would rate them a nine, only because occasionally the first person I talk to does not know more than I do and it needs to be escalated to reach someone more knowledgeable."
"It's very difficult to implement."
"While InfoScale is mainly used by enterprise-level customers, it does not inherently support many applications, which presents a scalability issue."
"Many customers can see the benefits of InfoScale, but they are usually not able to buy the products and solutions because of the licensing costs."
"My experience with pricing, setup cost, and licensing is that it is a bit expensive, but rather than that, because it is used in critical environments with no competitor, most of the customers go for it anyways."
"It could be more stable and more secure."
"My experience with pricing, setup cost, and licensing indicates that pricing is a little higher and should be reduced since most companies cannot afford it."
"Many customers can see the benefit of InfoScale, but they are usually not able to purchase the product because the license cost is very high."
 

Pricing and Cost Advice

"One needs to pay for the licenses, and it is an annual subscription model right now."
"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."
"Elastic Observability's pricing could be better for small-scale users."
"So far, there are just the standard licensing fees. Several of the components are embedded in the license or are even open source. They're even free depending on what you use, which makes it even more appealing to someone that is discussing pricing of the solution."
"Users have to pay for some features, like the alerts on different channels, because they are unavailable in different source versions."
"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."
"Pricing is one of those situations where the more you use it, the more you pay."
"Our clients pay for licensing on a yearly basis."
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
909,948 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
10%
Manufacturing Company
7%
Government
7%
Financial Services Firm
18%
Manufacturing Company
8%
Outsourcing Company
7%
Media Company
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 Business8
Midsize Enterprise3
Large Enterprise4
 

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.
What is your experience regarding pricing and costs for Veritas InfoScale Availability?
My experience with pricing, setup cost, and licensing is that it is a bit expensive, but rather than that, because it is used in critical environments with no competitor, most of the customers go f...
What needs improvement with Veritas InfoScale Availability?
InfoScale can be improved if it added more robust reporting features; it has reporting, but it is very simple. If it created an integration with a reporting tool that makes it official, customers c...
What is your primary use case for Veritas InfoScale Availability?
My main use case for InfoScale is that we use it in many scenarios. In some scenarios, we use it for clustering for a product like Enterprise Vault, using InfoScale Enterprise, where we handle the ...
 

Also Known As

No data available
Veritas InfoScale Availability, Arctera InfoScale for Kubernetes
 

Overview

 

Sample Customers

PSCU, Entel, VITAS, Mimecast, Barrett Steel, Butterfield Bank
Wayne State University, Zenith Mart
Find out what your peers are saying about Elastic Observability vs. InfoScale and other solutions. Updated: July 2026.
909,948 professionals have used our research since 2012.