feat (AI): Add new Sentry in AI section to docs#16311
feat (AI): Add new Sentry in AI section to docs#16311
Conversation
- Fix bug where frontmatter wasn't showing NEW badge
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
sfanahata
changed the title
- docs/ai/mcp.mdx: keep current client setup, add Advanced Features line from master - docs/ai/monitoring/agents/dashboard.mdx: merge intro text, use /ai/monitoring/agents/ links - docs/ai/monitoring/mcp/index.mdx: use overview-tab.png, fix getting-started link to /ai/monitoring/mcp/getting-started/ - docs/product/ai-in-sentry/index.mdx: drop duplicate AI Code Review, add AI Summaries and Privacy and security from master - Add docs/ai/monitoring/agents/costs.mdx from master with updated dashboard link - Keep all agent/mcp images in docs/ai/monitoring/ paths; add master’s new images (overview-tab, etc.) Co-authored-by: Cursor <cursoragent@cursor.com>
…, but otherwise, defered to Master.
…pdates from master - Add dotagents documentation page with beta badge and full quick start guide - Add dotagents LinkCard to the Sentry for AI landing page - Add dotagents as alternative install method in agent-skills docs - Sync agent-skills with sentry-agent-skills repo: add sentry-create-alert, remove unlisted sentry-nextjs-setup - Port OpenCode client setup and reauthentication troubleshooting from master MCP docs Co-Authored-By: Claude <noreply@anthropic.com>
codyde
changed the title
Co-Authored-By: Claude <noreply@anthropic.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 4 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| }, | ||
| { | ||
| from: '/product/sentry-mcp/', | ||
| to: '/ai/mcp/', |
There was a problem hiding this comment.
Missing redirect for deleted AI index page
High Severity
The docs/product/insights/ai/index.mdx file was deleted but no redirect was added from /product/insights/ai/ to the new location (e.g. /ai/monitoring/). This path will now 404. Worse, redirects.js line 1097 still redirects /product/insights/llm-monitoring/:path* to /product/insights/ai/, creating a broken redirect chain — users following that redirect will land on a 404.
| { | ||
| from: '/product/insights/ai/agents/getting-started/', | ||
| to: '/ai/monitoring/agents/getting-started/', | ||
| }, |
There was a problem hiding this comment.
Missing redirect for agents privacy page
Medium Severity
The agents privacy page moved from /product/insights/ai/agents/privacy/ to /ai/monitoring/agents/privacy/, but no redirect was added for the old path. The middleware has redirects for the sibling pages (dashboard, costs, getting-started) but not privacy, so the old URL will 404.
| { | ||
| from: '/product/insights/ai/mcp/getting-started/', | ||
| to: '/ai/monitoring/mcp/getting-started/', | ||
| }, |
There was a problem hiding this comment.
Missing redirect for MCP dashboard page
Medium Severity
The MCP dashboard page moved from /product/insights/ai/mcp/dashboard/ to /ai/monitoring/mcp/dashboard/, but no redirect was added. The middleware redirects the MCP index and getting-started pages but not the dashboard page, so the old URL will 404.
| ) | ||
| ), | ||
| LinkCard, | ||
| LinkCardGrid, |
There was a problem hiding this comment.
Redundant LinkCard registration in page component
Low Severity
LinkCard and LinkCardGrid are added to mdxComponentsWithWrapper explicitly on lines 65–66, but they're already included in the object returned by mdxComponents() (lines 135–136 of mdxComponents.ts). The spread already includes them, making the explicit additions redundant.
Additional Locations (1)
2 participants
DESCRIBE YOUR PR
Moving some of the documentation front and center around how Sentry integrates with agents (both in offering monitoring, and with tools like the MCP).
Preview: https://sentry-docs-git-sentry-in-ai.sentry.dev/ai/
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: