{"version":"2.1.275","anchor":"otel-metrics-exporter-headers-now-vary-by-protocol","canonical_anchor":"otel-metrics-exporter-headers-now-vary-by-protocol","heading":"OTEL metrics exporter headers now vary by protocol","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/otel-metrics-exporter-headers-now-vary-by-protocol","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### OTEL metrics exporter headers now vary by protocol\n\nOTEL metrics exporter now builds its request headers based on which protocol is in use\n\n**What**\n\nThe function that builds headers for the OpenTelemetry (OTEL) metrics exporter now also receives the resolved protocol string as an input, so the headers it produces can vary depending on which protocol is being used to send metrics.\n\n**Why**\n\nThis allows the metrics exporter to send protocol-appropriate headers instead of a single fixed set, which matters for anyone configuring OTEL metrics export with different transport protocols.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}