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.
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 …
The use of a single integration and definition of custom metrics, and tags is a great advantage. The ability to use SignalFlow to observe metrics in addition to the vast number of out-of-the-box dashboards is also excellent.
Its great if you need real-time visibility across complex or regulated environments. Also strong for hybrid or multi-cloud setups where uptime, observability and fast IR are required. It’s probably overkill for smaller teams or environments that don’t have constant changes or compliance reporting needs. It's expensive and has a steep learning curve. Also, in my opinion, do not get yourself into a consumption based model. Costs can certainly get out of control quickly.
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.
You can use table-like functionality to generate dashboards, but these queries are heavy on the system.
It could be easier to give insight into what type of line parsing is used for specific documents in a company-managed environment and/or show ways to gain the insights needed.
I would like to see ways to anonymize specific data for shared reports without pre-formatting this in a dashboard on which reports could be based.
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
When there is an issue, it’s a win if one can easily identify the root cause. To do the same, it should allow the user to dig deep with multiple data points and compare the data and identify the anomaly. In this use case, it’s good to drive from Splunk 011y.
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 of servers and agents residing together within a single data centre, but modern apps are no longer like this.