From the problem to the solution.
Situations that repeat in almost every monitoring and observability team, and how we tackle them with Splunk Observability Cloud and OpenTelemetry. Each case starts with the problem, not the product, and is based on the platform’s current documentation.
Every case follows the same path, from the first signal to the action.
- 01Signal
- 02Context
- 03Correlation
- 04Cause
- 05Decision
- 06Action
Technology
Splunk Observability Cloud
Module
-
Reference scenarioO11Y-01
We find out about outages from our customers
Measure from the outside what users actually experience and alert on symptoms, with the back-end trace to go straight to the cause. Splunk Observability Cloud · Synthetic Monitoring Synthetic Monitoring · APM · Detectors Executive and technical · 3 min readView the case -
Reference scenarioO11Y-02
Hundreds of CPU alerts, and none of them tells us the customer is affected
Alert on what users feel: errors, latency and SLO burn rate. Keep infrastructure thresholds for capacity, not for waking people up. Splunk Observability Cloud · Alerts and SLOs SLO · Detectors · APM Executive and technical · 3 min readView the case -
Reference scenarioO11Y-03
We have logs, metrics and traces… but they don't talk to each other
Share context between signals to go from a metric to its trace, and from the trace to its log, without searching by eye. Splunk Observability Cloud · APM and logs APM · Related Content · Log Observer Connect · OpenTelemetry Technical · 3 min readView the case -
Reference scenarioO11Y-04
The service map shows “unknown_service”, or the same application five times
An OpenTelemetry attribute convention defined before deployment, so the map reflects the real architecture. Splunk Observability Cloud · OpenTelemetry OpenTelemetry · Collector · APM · Service map Technical · 3 min readView the case -
Reference scenarioO11Y-05
Users say the website is slow, but the back end looks fine
Measure the experience in the user's browser with RUM and follow a slow request to its back-end trace in APM. Splunk Observability Cloud · RUM RUM · APM · OpenTelemetry Technical · 3 min readView the case -
Reference scenarioO11Y-06
Our metric volume keeps growing and nobody knows which metrics we actually use
Find the high-cardinality metrics, keep the dimensions you query, and aggregate, archive or drop the rest with Metrics Pipeline Management. Splunk Observability Cloud · Metrics and cost Metrics Pipeline Management · Infrastructure Monitoring · Collector Executive and technical · 3 min readView the case -
Reference scenarioO11Y-07
Our charts have gaps and we don't know if the Collector is losing data
Monitor the Collector itself: data accepted, refused and failed, queue usage and memory, so every gap in a chart has a known cause. Splunk Observability Cloud · OpenTelemetry OpenTelemetry Collector · Infrastructure Monitoring · Detectors Technical · 3 min readView the case
No cases match your search. Let’s talk about your case
Can’t find your case?
Tell us what’s happening on your platform. If it’s a common problem, it will be our next case.
Let’s talk about your case