Splunk Observability Cloud aims to enable operational agility and better customer experience through real-time AI-driven streaming analytics allowing accurate alerts in seconds. It is designed to shorten MTTD and MTTR by providing real-time visibility into cloud infrastructure and services.
$15
per month (billed annually) per host
Virtana
Score 8.8 out of 10
N/A
Virtana delivers enterprise-grade deep hybrid infrastructure observability, enabling organizations to achieve visibility and control across their entire IT estate. The platform unifies monitoring of on-premises, cloud, and Kubernetes environments, to transform complex infrastructure management into a strategic advantage. Core Platform Capabilities Deep Infrastructure Observability: · Automated topology discovery and mapping · Real…
$0
Pricing
Splunk Observability Cloud
Virtana
Editions & Modules
Infrastructure
$15
per month (billed annually) per host
App & Infra
$60
per month (billed annually) per host
End-to-End
$75
per month (billed annually) per host
Free
$0
Pro
$5
per month per device
Offerings
Pricing Offerings
Splunk Observability Cloud
Virtana
Free Trial
Yes
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Volume discounts are available (600+ devices / month)
A device is any running AWS EC2 or Azure VM evaluated by Virtana Optimize in a given month
it could stack up against this version of Splunk because in this instance of having the cloud option as an available use case it furthermore has more use cases and the options for the data to always be readily available will furthermore allows for analysts to review the data in …
Datadog pushes intom proprietary ecosystem and pricing structure.Compared to self hosted prometheus and grafarna but it gave headache og managing our own monitoring infrastructure at scale.Prometheus is excellent for scraping cluster metrics but it doesnt handle distributed …
I guess scale is the main factor against grafana and ease of use against amazon elasticsearch service and also i have used signoz and ELK Stack also, but stability Splunk Observability Cloud gives is too good and also it comes with high avability and you have to maintain …
We initially chose Splunk Observability Cloud because it promised full-stack visibility and tighter integration. The other tools didn't offer this as part of the core package. Their analytics and real-time dashboards looked strong during the demo but it turned out to a lot …
I selected Splunk Observability Cloud because it focused so much on OTEL standards which will help us in future as OTEL is covering most of the observability standards. And also it has the best Kubernetes observability as I already explained it has several predefined dashboards …
Splunk Observability Cloud stood out for its real-time data ingestion, native OpenTelemetry support, and seamless correlation between metrics, traces, and logs, which gave us faster root cause analysis and better end-to-end visibility compared to Grafana setups that required …
To be honest, Datadog is very similar to Splunk and LogScale to a lesser degree, but it is just as good if you don't need too complex observability. Grafana is still growing and might reach the same level soon.
It's able to quickly detect and resolve issues across the entire spectrum of deployments including on-premises, public cloud, private cloud, hybrid cloud and multicloud
The above applications have their own use cases. Thousand Eyes or Sitescope is used for URL monitoring and Splunk is used for application monitoring. Appdynamics is also used for application monitoring and can monitor the server very well but it lacks when searching in logs …
Splunk is superior in many ways to these solutions when I'm comes to ingesting, storing, manipulating, and using data, but dynatraces automatic agents do make it much easier to use out of the box. Nagios seems much cheaper but does not provide as much functionality as Splunk. …
SQL is a great tool for smaller quick checks. When trying to monitor several different environments, applications, APIs, several thousand devices, connections, and technology, it just doesn't stand up to what you need. Splunk Infrastructure Monitoring has really stood out …
We are having other monitoring tools like AppDynamics, Dynatrace, Datadog and already using their end-user monitoring capability. Most of our customers are looking for agent-free monitoring where they don't want to instrument any agent on their client-side (as it might …
Splunk Infrastructure Monitoring provides far superior options for anybody using a complex hybrid multi-cloud environment and allows both your SOC and NOC to work together on the same data while driving their own insights.
We found other products are still in the old world view …
We selected Zenoss because we had been using it for years before these other solutions were considered nearly robust enough to potentially be a viable alternative to Zenoss. Our familiarity with the interface and the tool set made it an easy choice for us to continue to …
We don't have much to say bad about other services. We just found that Metricly was a good fit for us. And their customer support is really really good. So if we get stuck we simply reach out for help which hasn't been very often. We didn't get that kind of support from other …
We strongly prefer Metricly for AWS Cost Analysis -- whereas other tools are easier to use on a traditional monitoring basis. To be clear, Merticly's monitoring tools are GREAT, but they require tuning and manual setup that we didn't have the time for on a small Platform …
Good for below cases 1. There is a front end and need to correlate data with front end data 2. multiple microservices and need to check the health of each system 3. correlate data from various sources 4. Application performance is a key to be captured 5. application performance is a key metric.
Zenoss is one of the most economical low cost monitoring/AIOPS tools available in the market. This goes excellent when complete infra is monitoring by itself however if its receiving the events from other monitoring tool then the Event management uses cases will be limited.
The first one is its Kubernetes container monitoring.
I really like this features because as we know how much K8s is vast and to manually monitor each part of the Kubernetes it takes so much time but Splunk Observability Cloud makes it easier. And even once we integrate K8s with Splunk Observability Cloud it gives us some prebuilt dashboards which gives holistic view of our Cluster and its nodes, pods, etc.
The dashbaord feature of Splunk Observability Cloud, it gives us full flexibility to customize our dashboard with a wide range of predefined chart types.
Now it also supports OTEL, which is a plus point for observability. As now everyone is moving towards Otel and in current market there are only few tools who supports OTEL based integrations, Splunk Observability Cloud is one out of them.
An indicator for errors on the navigations pane so that we don't have to go through each tab.
As we go more and more cloud maybe you guys can implement a pay-as-you-use strategy so that small companies using it not frequently can also afford it.
That's it can't think of any and it wont let me skip to next question. Thanks
Support for streaming data is on the roadmap must currently be addressed via a third-party app.
For some customers, a hybrid on-prem/cloud model may be a better fit than a pure cloud model. The onsite collectors offer some, but not all, of this functionality.
Good: Stable system with low error rate Easy to use for simple use cases Bad: UI is not very clear for complex usage Mobile view (when logged in from phone) is bad No library for .net
Overall a great tool to have in your toolbox, It is very intuitive and our entire staff uses the tool. It is easy to use and cost is very reasonable. Splunk also has excellent support team and very easy to work with. Every time we had a challenge, support team was able to help us with the end result.
To be honest, Datadog is very similar to Splunk and LogScale to a lesser degree, but it is just as good if you don't need too complex observability. Grafana is still growing and might reach the same level soon.
We selected Zenoss because we had been using it for years before these other solutions were considered nearly robust enough to potentially be a viable alternative to Zenoss. Our familiarity with the interface and the tool set made it an easy choice for us to continue to upgrade and use the product.