{"version":"2.1.269","anchor":"otlp-telemetry-endpoint-validation-now-accepts-grpc-style-sc","canonical_anchor":"otlp-telemetry-endpoint-validation-now-accepts-grpc-style-sc","heading":"OTLP telemetry endpoint validation now accepts gRPC-style schemes","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/otlp-telemetry-endpoint-validation-now-accepts-grpc-style-sc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### OTLP telemetry endpoint validation now accepts gRPC-style schemes\n\nTelemetry endpoint settings now accept gRPC-style URL schemes like grpc, otlp and tcp, not just http\/https\n\n**What**\n\nWhen Claude Code checks the OTLP (OpenTelemetry Protocol, a standard format for exporting telemetry data) endpoint environment variables `ANT_OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_*_ENDPOINT`, it now accepts a wider range of URL schemes: `grpc`, `grpcs`, `otlp`, `xds`, `tcp`, `udp`, `tls`, `h2`, `h2c`, and `http2`, in addition to the previously accepted `http` and `https`.\n\n**Why**\n\nThis avoids Claude Code incorrectly flagging a valid gRPC-based or other non-HTTP telemetry endpoint URL as misconfigured, which matters if your telemetry collector is set up to receive data over one of these protocols instead of plain HTTP.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}