Configure the OpenTelemetry Collector to Ingest Prometheus Metrics

Now that you’ve installed the OpenTelemetry Operator for Kubernetes, you can configure the Collector with Lightstep’s example Helm chart for a single-replica deployment.

  1. From the Lightstep otel-collector-charts repository, copy the charts/collector_k8s folder to your existing directory.
    git clone
  2. Set the shell variable LS_TOKEN to your Lightstep Access Token.
    export LS_TOKEN="<ACCESS_TOKEN>"
  3. Understand the current configuration
    cat ./charts/collector-k8s/values.yaml

    By default, the single deployment collector is configuring to accept OTLP traces and metrics, as well as scrape its own custom metrics using Prometheus. It uses the memory limiter to prevent OOMs, and the batch processor to improve performance.

    Be sure to change the name in the values file for the collector to something more descriptive.

  4. Configure a single-replica collector using Lightstep’s example Helm chart for the OpenTelemetry Operator for Kubernetes.
    kubectl create namespace opentelemetry
    kubectl create secret generic otel-collector-secret -n opentelemetry --from-literal=LS_TOKEN=$LS_TOKEN
    helm upgrade lightstep ./charts/collector-k8s -f ./charts/collector-k8s/values.yaml -n opentelemetry --install
  5. In Lightstep Observability, use a Notebook to verify that the metric otelcol_process_uptime is reporting to your Lightstep project. Verifying OpenTelemetry Installation

If you don’t see this metric, you might not have set your token correctly. Check the logs of your Collector pod for access token not found errors using: % kubectl logs -n opentelemetry <collector pod name> If you see these errors, make sure that the token saved in your otel-collector-secret is correct and has write metrics permissions.


The default OTLP Exporter from a Collector enables gzip compression and TLS. Depending on your network configuration, you may need to enable or disable certain other gRPC features. This page contains a complete list of configuration parameters for the Collector gRPC client.

In the event that you are unable to establish a gRPC connection to the Lightstep Observability platform, you can use the grpcurl tool to ensure connectivity from your network to our public satellites. Run the following command, replacing <YOUR_ACCESS_TOKEN> with your project’s access token:

grpcurl -H 'lightstep-access-token:<YOUR_ACCESS_TOKEN>' list

You should see the following output, or something similar:


If you do not see this output, or the request hangs, then something is blocking gRPC traffic from transiting your network to ours. Please ensure that any proxies are passing through the lightstep-access-token header.

For additional troubleshooting recommendations, see Troubleshooting Missing Data in Lightstep.

What Did we learn?

  • We configured the collector using the Kubernetes Operator for OpenTelemetry