Start getting data in to Splunk Observability Cloud 🔗
This page provides an overview for configuring integrations in Splunk Observability Cloud to collect metrics, logs, and spans from your infrastructure and services.
You must be an administrator to configure integrations in Observability Cloud. Each integration walks you through a step-by-step process to collect supported data types. To configure an integration for any data source, select Navigation menu > Data Setup.
The following steps describe how to configure integrations that collect metrics, logs, and spans from your infrastructure and services.
Step 1. Connect cloud services
Connect your cloud service provider to collect metrics and logs from supported cloud services. Observability Cloud provides integrations for AWS, GCP, and Azure.
To connect your cloud service provider, select Navigation menu > Data Setup and search for the cloud service you want to connect to.
See the following documentation for more information on connecting cloud services to Observability Cloud:
Step 2. Collect infrastructure data with an OpenTelemetry Collector
Observability Cloud provides supported integrations for Kubernetes, Linux, and Windows. Integrations for these data sources help you deploy a Splunk OpenTelemetry Collector to export metrics and logs from hosts and containers to Observability Cloud.
Splunk provides several methods to install and configure the Splunk OpenTelemetry Connector. The Splunk OpenTelemetry Connector is a package that provides integrated collection and forwarding for all data types for a specific platform. “Connector” refers to packaging only, which is separate from the standalone Splunk Distribution of OpenTelemetry Collector. The connector includes the Splunk Distribution of OpenTelemetry Collector.
To collect metrics and logs from an infrastructure resource, select Navigation menu > Data Setup and select the host type or containerized environment you want to collect metrics and logs from. See Install the collector for more information about the host types or containerized environments packaged as connectors.
If you plan to instrument your applications to collect spans and trace data (Step 3), first configure an integration to deploy the connector on the host or containerized environment that each service is running in.
For more information on sending host or container metrics and logs to Observability Cloud, see the following documentation:
Step 3. Export spans from services with OpenTelemetry instrumentation
If you want to use Observability Cloud’s APM capabilities, you need to apply language-specific instrumentation packages to each service. Each of these packages contains a Splunk distribution of OpenTelemetry instrumentation based on the service’s language. If you did not deploy an OpenTelemetry Collector (Step 2) on the host or in the Kubernetes cluster the service is running in, do that first.
Once you’ve instrumented an application or service, Observability Cloud starts receiving trace data from the OpenTelemetry Collector running on the host or in the Kubernetes cluster. How you specify the OpenTelemetry Collector endpoint depends on the language you are instrumenting. For more information, see the documentation for the language you are instrumenting.
See the following documentation for more information about the language you want to instrument: