docs(js): Move AI Agent Monitoring to top-level feature #16112
Closed
Conversation
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
Creates a dedicated tracing guide for Next.js that addresses: - Auto-instrumentation by runtime (client/server/edge) - Server Actions requiring withServerActionInstrumentation - Web Vitals capture - Custom instrumentation patterns - Distributed tracing configuration - Common troubleshooting scenarios Follows the technical-docs skill principles: lead with "why", structure by user intent, avoid redundancy. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add tracing concept link in intro - Add Prerequisites section - Reorder sections logically (Prerequisites → Enable → What's Traced) - Fix Web Vitals section: remove empty code block, add FCP/TTFB, add product links - Remove incorrect Disable Tracing section - Remove redundant troubleshooting items (already covered in Server Actions section) - Fix tracesSampler example to use attributes available at transaction start Co-Authored-By: Claude <noreply@anthropic.com>
Add cross-references to common tracing docs for users who want deeper details: - Automatic Instrumentation (timeouts, INP, span filtering) - Custom Instrumentation (full span API) - Distributed Tracing (CORS, manual propagation) Co-Authored-By: Claude <noreply@anthropic.com>
Move AI Agent Monitoring from /tracing/instrumentation/ai-agents-module/ to a new top-level /ai-agent-monitoring/ feature across all JavaScript SDKs. - Create new ai-agent-monitoring directory with index.mdx and browser.mdx - Add redirects from old paths to new paths - Update internal links in Next.js docs and product docs - Delete old ai-agents-module files Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
- Add SplitLayout pattern for better code/text presentation - Add Prerequisites section linking to tracing setup - Add Options section documenting recordInputs/recordOutputs - Wrap all span examples in SplitLayout for side-by-side view Co-Authored-By: Claude <noreply@anthropic.com>
Member
Author
|
Superseded by #16117 (clean branch with only AI Monitoring changes) |
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
Move AI Agent Monitoring from
/tracing/instrumentation/ai-agents-module/to a new top-level/ai-agent-monitoring/feature across all JavaScript SDKs.Changes:
ai-agent-monitoringdirectory withindex.mdxandbrowser.mdxai-agents-modulefilesThis makes AI Agent Monitoring a first-class feature in the sidebar (like Logs, Tracing) instead of being nested under tracing instrumentation.
IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST