Skip to content

llm_observability: document prompt_uuid for OTel Prompt Tracking - #39675

Draft
yahya-mouman wants to merge 2 commits into
masterfrom
yahya.mouman/prompt-tracking-prompt-uuid
Draft

llm_observability: document prompt_uuid for OTel Prompt Tracking#39675
yahya-mouman wants to merge 2 commits into
masterfrom
yahya.mouman/prompt-tracking-prompt-uuid

Conversation

@yahya-mouman

@yahya-mouman yahya-mouman commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Adds prompt_uuid and prompt_version_uuid to the field tables for:

  • OpenTelemetry Prompt Tracking (the _dd.ml_obs.prompt_tracking span attribute)
  • The Agent Observability HTTP API's Prompt object

Both tables previously documented only id/name/version (plus template, variables, and RAG fields). If a prompt is fetched from the Prompt Management registry (for example, through the Prompt Management REST API, in a language without a native Agent Observability SDK) and then tagged onto a span through OTel or the raw HTTP API, id/version alone aren't enough for that span to link back to its Prompt Management registry entry in the Prompts view. This PR adds the two missing fields to both tables and a short note explaining when they're needed.

Merge readiness

  • Ready for merge

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
  • 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Used to draft the field-table wording and confirm field usage before proposing this docs change.

Additional notes

Adds prompt_uuid and prompt_version_uuid to the OpenTelemetry Prompt
Tracking field table. Without these, a span tagged via the
_dd.ml_obs.prompt_tracking OTel attribute is tracked but does not link
back to its Prompt Management registry entry in the Prompts view -
this matters for any language without a native Agent Observability
SDK (e.g. .NET) using the REST Prompt Management API alongside plain
OTel instrumentation.
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Adds prompt_uuid and prompt_version_uuid to the Agent Observability
HTTP API's Prompt schema table, matching the OTel Prompt Tracking
field table update in this PR. Without these, a prompt submitted
through the raw Spans API is tracked but does not link back to its
Prompt Management registry entry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant