sentry-otel-exporter-setup

To send traces to Sentry, configure the OpenTelemetry Collector using the Sentry Exporter. This involves generating a collector-config.yaml file that includes environment placeholders for your Sentry organization slug and authentication token to route telemetry data.

Yes, you can route telemetry from multiple services to corresponding Sentry projects automatically. The Sentry Exporter configuration supports multi-project environments, enabling automatic project creation when missing projects receive their first telemetry data.

You set up environment placeholders by defining variables like SENTRY_ORG_SLUG and SENTRY_AUTH_TOKEN in your collector-config.yaml. The setup steps provide clear instructions on obtaining these real values to ensure secure handling of your Sentry credentials.

Yes, the configuration includes a debug and logging pipeline to troubleshoot Sentry telemetry routing. This debug path allows you to verify telemetry flow and validate the collector-config.yaml before running the full export operation.

The best way to validate the collector-config.yaml is by using the built-in validation steps provided during configuration. This ensures your Sentry Exporter setup is correct and verifies the telemetry flow before you run the collector.