Skip to content
Latchkey

How to Export Build Traces to Honeycomb

Honeycomb speaks OTLP directly, so a trace exporter only needs the ingest URL and an API key header to land spans.

Honeycomb ingests OTLP over gRPC at api.honeycomb.io:443 and over HTTP at https://api.honeycomb.io. Authenticate with the x-honeycomb-team header carrying your ingest key, and set x-honeycomb-dataset to name the dataset.

Steps

  • Create an ingest API key in Honeycomb.
  • Set OTLP_ENDPOINT to the Honeycomb OTLP URL.
  • Send the key in the x-honeycomb-team header and name the dataset.

Exporter config

.github/workflows/otel.yml
- uses: corentinmusard/otel-cicd-action@v2
  with:
    otlpEndpoint: https://api.honeycomb.io
    otlpHeaders: "x-honeycomb-team=${{ secrets.HONEYCOMB_KEY }},x-honeycomb-dataset=ci"
    githubToken: ${{ secrets.GITHUB_TOKEN }}
    runId: ${{ github.event.workflow_run.id }}

Verify from a terminal

Terminal
curl https://api.honeycomb.io/1/auth \
  -H "X-Honeycomb-Team: $HONEYCOMB_KEY"

Related guides

Run this faster and cheaper on Latchkey managed runners. Start free →