Uh oh!
There was an error while loading. Please reload this page.
dev-docs (MCP server): Add tracing and errors documentation - #14374
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
AbhiPrasad
left a comment
There was a problem hiding this comment.
nice, this is what I think we want. Once we convert the errors spec to stop using tags we can merge!
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
coolguyzone
left a comment
There was a problem hiding this comment.
Looks good! Thanks for adding 🫡
Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>
….mdx Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>
….mdx Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>
betegon
commented
Jul 22, 2025
Hey @coolguyzone , thanks for reviewing it. I was waiting to update the erors docs to use |
AbhiPrasad
left a comment
There was a problem hiding this comment.
very happy with this, good starting point. Thanks for iterating @betegon
betegon
commented
Jul 25, 2025
merging this, happy to push another PR if you review it @coolguyzone :) |
Uh oh!
There was an error while loading. Please reload this page.
## DESCRIBE YOUR PR Closes#14106 Adds developer docs for our MCP Server instrumentation. Route for the documentation `sdk/expected-features/mcp-instrumentation` that includes: ```bash .mcp-instrumentation ├── index.mdx # brief description on current features and limitations ├── errors.mdx # draft errors doc └── tracing.mdx # Tracing and span conventions ``` Followed this file structure as a start to (in the future) have this structure for all the other features, having something like this below, where we have : ``` .[Feature 1] ├── index.mdx ├── logs.mdx ├── errors.mdx . . . .[Feature 2] ├── index.mdx ├── errors.mdx ├── tracing.mdx . . . ``` The structure idea is from @abhi, who helped me settle this <3. **NOTE:** Error docs are going to change, addressing feedback from [sentry-javascript/pull/16817](getsentry/sentry-javascript#16817) ## IS YOUR CHANGE URGENT? ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [x] 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) --------- Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>
DESCRIBE YOUR PR
Closes#14106
Adds developer docs for our MCP Server instrumentation.
Route for the documentation
sdk/expected-features/mcp-instrumentationthat includes:Followed this file structure as a start to (in the future) have this structure for all the other features, having something like this below, where we have :
The structure idea is from @abhi, who helped me settle this <3.
NOTE: Error docs are going to change, addressing feedback from sentry-javascript/pull/16817
IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: