What it does
Splunk Observability Cloud is Splunk's hosted suite for infrastructure monitoring, application performance monitoring, real-user monitoring, and synthetic checks. It accepts telemetry through OpenTelemetry and other integrations, correlates traces and metrics with logs held in Splunk Platform through Log Observer Connect, and presents data through dashboards, detectors, and SLOs. A free edition is advertised for up to 15 hosts, while paid editions add capabilities on host-based plans.
A hosted suite for operational telemetry
Splunk Observability Cloud brings infrastructure monitoring, Splunk APM, real-user monitoring, synthetic monitoring, and alerting into a single service. Its dashboards and trace views help teams investigate service and infrastructure behavior. For log context, Log Observer Connect connects to application and infrastructure logs already stored in Splunk Platform; it is not a claim that the Observability Cloud service itself replaces Splunk Enterprise or Splunk Cloud Platform.
Getting data into the service
A sensible first project is to monitor one host or instrument one backend service. Splunk's getting-data guide separates the work into infrastructure and cloud services, application and function instrumentation, user-interface instrumentation, and custom data sent through the Observability Cloud API. The Splunk Distribution of the OpenTelemetry Collector can run in host-monitoring mode beside an application or in gateway mode as a separate service. Its configuration defines receivers, processors, and exporters, then connects them in pipelines; the components do not run simply because they appear in the config.
For a Collector setup, the documentation calls for an organization access token with ingest authorization, the organization's realm, and the relevant ports and endpoints. After telemetry is flowing, use Infrastructure Monitoring or APM to inspect the incoming signals, create charts or dashboards, and define detectors and SLOs for conditions the team wants to track. A service team could, for example, use a trace to locate a slow dependency and check related infrastructure metrics before deciding what to change.
The service also documents a broad REST API. The reference covers ingestion, charts, detectors, dashboards, service topology, and SLOs. API calls require a valid organization or session token and permissions appropriate to the operation, so programmatic access is not anonymous.
Product boundaries and pricing
Splunk's pricing page lists an Observability Cloud Free Edition and paid Infrastructure, App & Infra, and End-to-End plans priced by host. The dedicated Free Edition page says it supports up to 15 hosts, is not a time-limited trial, and does not require a credit card; its current description highlights Agent Observability. Do not assume that the free edition includes every feature shown in the paid plan comparison.
This listing is for Splunk Observability Cloud itself, not Splunk Enterprise, Splunk Cloud Platform, AppDynamics, IT Service Intelligence, or Splunk On-Call. Teams need to supply their own services, infrastructure, or user journeys to monitor and configure telemetry collection.
Strengths
- Combines infrastructure monitoring, APM, real-user monitoring, synthetic monitoring, detectors, and SLOs in a hosted observability service.
- Uses the Splunk Distribution of the OpenTelemetry Collector to receive, process, and export telemetry, with documented host and gateway deployment modes.
- Can correlate metrics and traces with logs already stored in Splunk Platform through Log Observer Connect.
- Provides documented APIs for telemetry ingestion and management of charts, detectors, dashboards, and SLOs.
Watch out for
- Collector onboarding requires configuring receivers, processors, and exporters into pipelines and supplying an access token, realm, and reachable endpoints.
- Log Observer Connect is aimed at logs already stored in Splunk Platform, so teams without that separate data source should not assume it provides a standalone log store.
- The free edition is limited to 15 hosts and currently highlights Agent Observability.
Best for
- SRE and platform teams that need hosted infrastructure monitoring and distributed application tracing.
- Teams standardizing telemetry collection on OpenTelemetry and using a managed monitoring backend.
- Organizations that already store operational logs in Splunk Platform and want to relate them to metrics and traces.
- Application teams that need real-user or synthetic monitoring in addition to service and infrastructure signals.
Sources
- Splunk Observability Cloud (Oct 25, 2026)
- Splunk Observability Cloud documentation (Oct 25, 2026)
- Get started guide to get data into Splunk Observability Cloud (Oct 25, 2026)
- Get started with the Splunk Distribution of the OpenTelemetry Collector (Oct 25, 2026)
- Splunk pricing (Oct 25, 2026)
- Splunk Observability Cloud Free Edition (Oct 25, 2026)
- API Reference | Splunk Developer Program (Oct 25, 2026)