Splunk Observability Cloud From Complexity to Clarity
Use Cases and Deployment Scope
It solves so many problems like End to End Visibility, Real time correlations to reduce MTTD etc.
Pros
- 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.
Cons
- It can improve its pricing models as per its competitors as I have it is a bit costly as compare to others.
- It can improve on its OTEL based integration part as currently to integrate OTel based application we need a good knowledge of OTel SDKs.
Likelihood to Recommend
Real time incident detection and Root cause analysis . due to this feature you can easily reduce this mttd and mttr.
