Skip to content

Migrate from Honeycomb to Logfire

Honeycomb is OpenTelemetry-native — you already send OpenTelemetry Protocol (OTLP) data, authenticated with the x-honeycomb-team header, to api.honeycomb.io (or api.eu1.honeycomb.io for EU). Migrating to Logfire swaps the endpoint and that header for Logfire’s Authorization header. Nothing else changes; see Migrate to Logfire for the general shape.

You’ll need a Logfire write token and your region endpoint (https://logfire-us.pydantic.dev or -eu).

If your apps export OTLP

Point the SDK’s OTLP variables at Logfire and replace the Honeycomb team header with Authorization:

Terminal
# before (Honeycomb):
#   OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io
#   OTEL_EXPORTER_OTLP_HEADERS='x-honeycomb-team=your-honeycomb-key'
export OTEL_EXPORTER_OTLP_ENDPOINT=https://logfire-us.pydantic.dev
export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
export OTEL_EXPORTER_OTLP_HEADERS='Authorization=your-write-token'
export OTEL_SERVICE_NAME=your-service-name

If you run the OpenTelemetry Collector

Change the Honeycomb exporter’s endpoint and header to Logfire’s:

exporters:
  otlphttp/logfire:
    endpoint: "https://logfire-us.pydantic.dev"  # or https://logfire-eu.pydantic.dev
    headers:
      # was: "x-honeycomb-team": "your-honeycomb-key"
      Authorization: "Bearer ${env:LOGFIRE_TOKEN}"

service:
  pipelines:
    traces:
      exporters: [otlphttp/logfire]
    metrics:
      exporters: [otlphttp/logfire]
    logs:
      exporters: [otlphttp/logfire]

To cut over gradually, keep both exporters in the pipeline and compare the same traffic in each before removing Honeycomb.

Verify

Run your workload and open the Live view. Traces should appear within seconds.

See also