From cd5627fd1cf46c67b8764de846f0efb38672eb79 Mon Sep 17 00:00:00 2001 From: Yordis Prieto Date: Thu, 17 Sep 2026 15:40:05 -0400 Subject: [PATCH] docs(fork): 0018 no longer claims T3 Code has no header or protocol names Signed-off-by: Yordis Prieto --- docs/fork/0018-the-standard-otel-variables-are-honored.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/fork/0018-the-standard-otel-variables-are-honored.md b/docs/fork/0018-the-standard-otel-variables-are-honored.md index 553aaa52d104..e3111c8beb3d 100644 --- a/docs/fork/0018-the-standard-otel-variables-are-honored.md +++ b/docs/fork/0018-the-standard-otel-variables-are-honored.md @@ -32,9 +32,11 @@ T3 Code has had a real OTLP exporter for a while, and it was unreachable for almost everyone who wanted it. You had to learn a second set of names for -settings you had already configured once, and headers, resource attributes, and -the wire format had no names at all, so an authenticated collector or a -protobuf-only one simply could not be used. +settings you had already configured once, and the standard names for headers, +resource attributes, and the wire format reached nothing, so an authenticated +collector or a protobuf-only one simply could not be used. T3 Code has its own +header and protocol names now, but the standard ones still arrive through this +divergence. The cost of that shows up as silence rather than as an error. Someone with a collector in their shell profile reasonably assumes the app found it, sees a