Docs » Supported integrations in Splunk Observability Cloud » Collect infrastructure metrics and logs » Collect Kubernetes data

Collect Kubernetes data 🔗

The Splunk Distribution of the OpenTelemetry Collector provides integrated collection and forwarding for all Kubernetes telemetry, such as metrics, APM traces, and logs, to Splunk Observability Cloud.

By default, the Collector for Kubernetes is deployed using a Helm chart. In a Kubernetes cluster, the chart creates a Kubernetes DaemonSet as well as other Kubernetes objects.

Supported versions 🔗

This Kubernetes solution has been validated in Kubernetes environments that use Minikube, Amazon Elastic Kubernetes Service (Amazon EKS), and Google Kubernetes Engine. See more details at Supported Kubernetes distributions.

Install the Collector for Kubernetes 🔗

To start the Kubernetes integration, follow these steps:

  1. Log in to Splunk Observability Cloud.

  2. Open the Kubernetes guided setup . Optionally, you can navigate to the guided setup on your own:

    1. In the navigation menu, select Data Management.

    2. Go to the Available integrations tab, or select Add Integration in the Deployed integrations tab.

    3. Select Kubernetes.

    4. Select Add Connection. The integration guided setup appears.

  3. Follow the steps in the guided setup.

Advanced install 🔗

For advanced installation instructions, see Install the Collector for Kubernetes using Helm.

This includes details about:

Check your access tokens 🔗

Access tokens are organization-level tokens that, by default, are valid for one year. For access tokens created prior to February 28, 2022, the expiration date remains 5 years from the creation date.

You must use an org token to authenticate emitters that send data points to Splunk Observability Cloud. You can use an org token in long-running scripts that call the API.

For more information, see Create and manage organization access tokens using Splunk Observability Cloud.

Learn more 🔗

This page was last updated on May 08, 2024.