{"version":"2.1.232","anchor":"more-opentelemetry-environment-variables-passed-through","canonical_anchor":"more-opentelemetry-environment-variables-passed-through","heading":"More OpenTelemetry environment variables passed through","tier":"use","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/more-opentelemetry-environment-variables-passed-through","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### More OpenTelemetry environment variables passed through\n\nYou can now set standard OpenTelemetry compression and per-signal protocol variables and have them respected.\n\n**What**\n\nThe list of environment variables Claude Code recognises now covers OTLP compression and per-signal protocol and temporality settings, so telemetry exporters can be configured with the standard OpenTelemetry names.\n\n**Details**\n\n- Added names include `OTEL_EXPORTER_OTLP_COMPRESSION`, `OTEL_EXPORTER_OTLP_LOGS_COMPRESSION`, `OTEL_EXPORTER_OTLP_TRACES_COMPRESSION`, `OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE` and `OTEL_EXPORTER_OTLP_TRACES_PROTOCOL`.\n\n**Evidence**\n\n`OTEL_EXPORTER_OTLP_TRACES_COMPRESSION`\n\n- Area: Telemetry\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}