From b8733297119e5af9f1d0810d4eed0576f5c76899 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 20 May 2026 13:35:33 +0000 Subject: [PATCH] Cross-reference OTLP metadata attachment from metadata docs The metadata page only covered the SDK and REST API paths. Now that PromptLayer ingests metadata from OpenTelemetry span attributes (user.id, gen_ai.conversation.id, promptlayer.metadata.*), add a section pointing OTLP users to the dedicated OpenTelemetry guide. https://claude.ai/code/session_01WesPFyrXFLqXrTZHCXP9xN --- features/prompt-history/metadata.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/features/prompt-history/metadata.mdx b/features/prompt-history/metadata.mdx index 5506395..5f934a8 100644 --- a/features/prompt-history/metadata.mdx +++ b/features/prompt-history/metadata.mdx @@ -90,3 +90,9 @@ Once metadata is added, you will then be able to see it in the web UI. ![score](/images/metadata-ui.png) Metadata is optimized for high-cardinality, request-specific values such as user IDs, session IDs, and error messages. For a smaller set of categories, such as environment, app, feature, or pipeline stage, use [tags](/features/prompt-history/tagging-requests) instead. + +## Attaching metadata via OpenTelemetry + +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.