{"version":"2.1.265","anchor":"telemetry-relay-can-forward-individual-signal-types-instead","canonical_anchor":"telemetry-relay-can-forward-individual-signal-types-instead","heading":"Telemetry relay can forward individual signal types instead of always OTLP for all three","tier":"use","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/telemetry-relay-can-forward-individual-signal-types-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Telemetry relay can forward individual signal types instead of always OTLP for all three\n\nTelemetry export can now send metrics, logs, and traces to different destinations instead of forcing all three to OTLP\n\n**What**\n\nThe `OTEL_METRICS_EXPORTER`, `OTEL_LOGS_EXPORTER`, and `OTEL_TRACES_EXPORTER` environment variables are now each computed individually based on the `telemetry.forward_to` configuration setting, rather than always being fixed to `\"otlp\"` (a standard telemetry export protocol).\n\n**Why**\n\nThis lets you route metrics, logs, and traces to different backends per signal type instead of being forced to send all three the same way, giving more flexible control over where telemetry data ends up.\n\n- Area: Telemetry\n- Names: `OTEL_METRICS_EXPORTER`, `OTEL_LOGS_EXPORTER`, `OTEL_TRACES_EXPORTER`, `telemetry.forward_to`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}