Splunk Observability Cloud unifies metrics, distributed traces, and logs to power real-time infrastructure and application monitoring.
Unlike Splunk Enterprise, which indexes immutable raw text events for retrospective search, Splunk Infrastructure Monitoring (IM) processes numeric Metric Time Series (MTS) in a streaming analytics engine. Because metrics carry compact numeric payloads and key-value metadata rather than verbose prose, Splunk Observability Cloud can ingest millions of datapoints per second with sub-second alerting latency.
Each telemetry pillar serves a distinct diagnostic purpose during an incident. Metrics tell you what is failing and trigger alerts when a service degrades; distributed traces follow individual requests across microservices to isolate which span caused latency or errors; logs provide rich forensic payload detail for root-cause verification; and Events capture discrete state changes such as code deployments or detector state transitions.
Metric -> cpu.utilization = 84.2 { host.name: "api-03", env: "prod" }
Trace -> trace_id: 9f2c... | span: POST /checkout (412ms, status=500)
Log -> 2026-11-20T02:00:01Z ERROR PaymentGateway timeout after 400ms
Event -> deploy v2.14.0 completed on service=checkout-api