sentry-otel-exporter-setup

Configure the OpenTelemetry Collector with the Sentry Exporter, which forwards traces and logs to Sentry. You need otelcol-contrib v0.145.0 or later, your Sentry organization slug, and an Internal Integration auth token set as environment variables.

Pull the otel/opentelemetry-collector-contrib image using the numeric version tag, then run it with your config file mounted as a volume and your .env file passed via --env-file. Expose ports 4317, 4318, and 13133 for OTLP and health checks.

The Sentry Exporter requires otelcol-contrib v0.145.0 or later. Check your installed version with the collector's version command, and upgrade by downloading a newer binary or pulling a newer Docker image if needed.

Yes, enabling auto_create_projects lets the exporter create Sentry projects from the service.name attribute. It requires at least one team in your Sentry org and Project: Write permission on the auth token; new projects are assigned to the first team found.

This error occurs when using the wrong token type or an expired token. Use an Internal Integration token created under Settings → Developer Settings → Custom Integrations, not a user auth token, with Organization: Read and Project: Read permissions.

Yes, OTLPIntegration is available for the Sentry Python, Ruby, and Node.js SDKs. It links OTel traces to Sentry errors, logs, crons, and metrics, and handles distributed tracing propagation automatically.