From acd38cc9bc222b7959dd35bf25dd615f4e43e02c Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 20 May 2026 13:41:56 +0000 Subject: [PATCH] Fix broken anchor in OTLP metadata cross-reference The heading "Attaching User Identity & Metadata" encodes the ampersand as %26 in the URL slug, so the correct anchor is #attaching-user-identity-%26-metadata. The previous link used a plain hyphen in place of the ampersand, causing users to land at the top of the OpenTelemetry page rather than the intended section. https://claude.ai/code/session_01WesPFyrXFLqXrTZHCXP9xN --- features/prompt-history/metadata.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/features/prompt-history/metadata.mdx b/features/prompt-history/metadata.mdx index 5f934a8..04666e6 100644 --- a/features/prompt-history/metadata.mdx +++ b/features/prompt-history/metadata.mdx @@ -95,4 +95,4 @@ Metadata is optimized for high-cardinality, request-specific values such as user If you instrument your app with OpenTelemetry, you can attach metadata directly from span attributes — no `track.metadata()` call required. PromptLayer automatically maps standard attributes like `user.id` and `gen_ai.conversation.id`, and also reads arbitrary `promptlayer.metadata.` attributes. -See [Attaching User Identity & Metadata](/features/opentelemetry#attaching-user-identity-metadata) in the OpenTelemetry guide for details. +See [Attaching User Identity & Metadata](/features/opentelemetry#attaching-user-identity-%26-metadata) in the OpenTelemetry guide for details.