Repository navigation
docs(agent-tracing): Update GenAI conventions - #19509
Merged
Merged
Conversation
Update the SDK convention reference with current message-part shapes, requirement keyword formatting, and canonical cached and reasoning token attributes. Keep general agent and pipeline requirements out of the tool-data table.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
Priority: Normal
1 of 3 tasks
obostjancic
changed the title
obostjancic
marked this pull request as ready for review
September 18, 2026 11:32
shellmayr
reviewed
Sep 18, 2026
shellmayr
approved these changes
Sep 18, 2026
Describe reasoning parts by their rendered behavior without treating Conversations view as a formal UI name.
obostjancic
enabled auto-merge (squash)
September 18, 2026 11:46
inventarSarah
pushed a commit
that referenced
this pull request
Sep 29, 2026
This was referenced Oct 6, 2026
sfanahata
added a commit
that referenced
this pull request
Oct 8, 2026
## DESCRIBE YOUR PR `pnpm build` and `pnpm build:developer-docs` both write to `.next`. When a PR touches both `docs/**` and `develop-docs/**`, the 404 workflow runs both builds in one job and then starts one server. By then the developer docs build has overwritten the docs build, so only developer docs get checked for broken links. This change gives each changed site its own job and runner: - A `changes` job decides which sites changed. - One `Lint <site> for 404s` job runs per changed site, in parallel. Each job builds, starts the server, and runs the linter. The runner is thrown away when the job ends, so the server doesn't need to be stopped and nothing else shares port 3000. - A small `lint-404` job keeps the required check name. It passes when every changed site passes its lint, or when no site changed. Changes to this workflow or `scripts/lint-404s/**` now lint both sites, so edits to the workflow check themselves. An earlier version of this PR handled the shared build with a bash script that started and stopped the server between sites. Separate jobs remove the need for it. PRs that touch both sites also run the two builds in parallel instead of one after the other. Replaces #19465. That PR's other changes already landed in #19509 (AI Agents doc) and #19526 (cross-site link handling). ## IS YOUR CHANGE URGENT? - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## PRE-MERGE CHECKLIST - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) <!-- junior-request-attribution:start --> via **shannon.anahata**. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AD0BB8KQT6MU%3A1791324850.904489 --> -- [View Junior Session](https://junior-prod.sentry.dev/conversations/slack%3AD0BB8KQT6MU%3A1791324850.904489) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AD0BB8KQT6MU%3A1791324850.904489/?project=4510944073809921) <!-- junior-session-footer:end --> --------- Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Shannon Anahata <shannon.anahata@sentry.io>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
The SDK Agent Tracing convention now documents current message-part shapes, including reasoning and tool-call parts, and uses the canonical cached-input and reasoning-output token attributes. RFC 2119 requirement keywords are formatted consistently.
Agent and pipeline names remain requirements for execute-tool spans but are not repeated in the tool-specific data table.
Split from #19461 so the developer-docs build and product-docs build run in separate PRs and do not overwrite each other's
.nextoutput.IS YOUR CHANGE URGENT?