Skip to content

feat(traces): Add agent tracing to trace explorer - #19271

Open
sfanahata wants to merge 1 commit into
masterfrom
docs/trace-explorer-agent-tracing
Open

feat(traces): Add agent tracing to trace explorer#19271
sfanahata wants to merge 1 commit into
masterfrom
docs/trace-explorer-agent-tracing

Conversation

@sfanahata

Copy link
Copy Markdown
Contributor

DESCRIBE YOUR PR

Add agent tracing to trace explorer

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace YYYY-MM-DD with the due date. You can update this information later by editing the PR description.

  • Urgent deadline (GA date, etc.): YYYY-MM-DD
  • Other deadline: YYYY-MM-DD
  • No deadline: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've supplied a deadline.

Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • 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

@vercel

vercel Bot commented Sep 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sentry-docs Ready Ready Preview Sep 3, 2026 10:43pm UTC
1 Skipped Deployment
Project Deployment Actions Updated
develop-docs Ignored Ignored Sep 3, 2026 10:43pm UTC

Request Review

@github-actions github-actions Bot added the Priority: Normal Docs review has no urgent deadline label Sep 3, 2026
@@ -42,6 +42,13 @@ The [**Trace Explorer**](https://sentry.io/orgredirect/organizations/:orgslug/tr

With these tools, the new Trace Explorer gives you powerful ways to understand your application's performance, identify bottlenecks, and make informed optimizations.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The new ### Agent Tracing (H3) section is placed between two ## Practical Examples (H2) sections, which breaks the required heading hierarchy and will cause sidebar rendering issues.
Severity: MEDIUM

Suggested Fix

To fix the broken heading hierarchy, either change ### Agent Tracing to an H2 heading (## Agent Tracing) to make it a main section, or move it to be a subsection under one of the ## Practical Examples sections. Alternatively, reorganize the duplicate Practical Examples sections to create a logical structure where the new section can be properly nested.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: docs/product/trace-explorer/index.mdx#L44

Potential issue: The new `### Agent Tracing` section, an H3 heading, is inserted between
two separate `## Practical Examples` H2 headings. This violates the documentation's
heading hierarchy rules, which require headings to be properly nested (e.g., an H3 must
be under an H2). According to the repository's own documentation guidelines, this
improper structure will cause the right-hand sidebar menu to fail to render correctly,
impacting site navigation for users viewing this page.

Did we get this right? 👍 / 👎 to inform future reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Priority: Normal Docs review has no urgent deadline

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant