Repository navigation
Update java-v9 branch - #20685
Update java-v9 branch#20685
Conversation
Adding user feedback retention period to the table.
## DESCRIBE YOUR PR The Java `maxRequestBodySize` option docs say the `small` cutoff "depends on the SDK (typically 4KB)". In the Java SDK, `small` captures request bodies smaller than 1,000 bytes and `medium` captures bodies smaller than 10,000 bytes. **Source evidence (sentry-java `8.62.0`):** `SentrySpringFilter.qualifiesForCaching` in [`sentry-spring-jakarta`](https://github.com/getsentry/sentry-java/blob/8.62.0/sentry-spring-jakarta/src/main/java/io/sentry/spring/jakarta/SentrySpringFilter.java#L121-L133) only caches the body when `(maxRequestBodySize == SMALL && contentLength < 1000) || (maxRequestBodySize == MEDIUM && contentLength < 10000) || maxRequestBodySize == ALWAYS`. `sentry-spring` and `sentry-spring-7` use the same check, and no other integration reads these sizes. **Corrected wording:** - `small`: Only small request bodies (smaller than 1,000 bytes) will be captured. - `medium`: Medium and small request bodies (smaller than 10,000 bytes) will be captured. cc @adinauer @romtsn @markushi @runningcode @0xadam-brown ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ <!-- junior-request-attribution:start --> via [automation `sched_fe39d4dd0d4e77a4b4463de325041d04`](https://junior-prod.sentry.dev/automations/sched_fe39d4dd0d4e77a4b4463de325041d04) · Run ID `sched_fe39d4dd0d4e77a4b4463de325041d04:1793692800000`. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:agent-dispatch%3Adispatch_d7b288a70af07fe5a018615bb57f884f --> -- [View Session](https://junior-prod.sentry.dev/conversations/agent-dispatch%3Adispatch_d7b288a70af07fe5a018615bb57f884f) [[Sentry]](https://sentry.sentry.io/explore/conversations/agent-dispatch%3Adispatch_d7b288a70af07fe5a018615bb57f884f/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
…0408) ## DESCRIBE YOUR PR In 7.0.0 the Serilog sink, NLog target and log4net appender no longer start Sentry. Apps that set the DSN there and also call `UseSentry` used to send crashes from before `UseSentry` started Sentry, and now drop them. This adds "Logging Integrations No Longer Report Startup Crashes" to the 6.x to 7.x migration guide, as a verify step in the interactive checklist. It shows the workaround from getsentry/sentry-dotnet#5847: call `SentrySdk.Init` at the top of `Main` as well, and capture the crash in a `catch`. Without the `catch`, an app with an async `Main` still drops the crash, because `using` disposes the first initialization before the exception reaches the runtime. "Logging Integrations No Longer Initialize Sentry" says to initialize Sentry once, so it now links to the new step. Checked on 7.0.0-rc.3 with a local stand-in for Sentry, crashing after `UseSentry` but before `Run()`: with the `catch`, a sync and an async `Main` each send the crash once. Without it, the async one sends nothing. getsentry/sentry-dotnet#5844 only covers Serilog. On 6.12.1 the NLog target and the log4net appender also sent a crash logged from `Main`, and on 7.0.0-rc.2 an NLog app with only `UseSentry` drops it, so the step covers all three. The links to the "Capturing Startup Crashes" sections of the Serilog, NLog and log4net guides land at the top of each page until #19925 adds them. Refs getsentry/sentry-dotnet#5844 Refs getsentry/sentry-dotnet#5710 ## 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. - [x] Urgent deadline (GA date, etc.): 2026-11-30 - [ ] Other deadline: YYYY-MM-DD - [ ] No deadline: Not urgent, can wait up to 1 week+ ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [x] Checked Vercel preview for correctness, including links - [x] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [x] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: James Crosswell <jamescrosswell@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
## DESCRIBE YOUR PR We were lacking a TL;DR on how our plans and trial work at the very top of the very long pricing page, so one has been added. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --------- Co-authored-by: Shannon Anahata <shannonanahata@gmail.com>
## DESCRIBE YOUR PR Documents the `gen_ai.extract` span in the agent tracing manual instrumentation guides, modeled on the existing Decision and Memory span sections. Follows [sentry-conventions#728](getsentry/sentry-conventions#728), which adds the experimental `gen_ai.extract` op, the `extract` operation name, and the extraction shapes for `gen_ai.input.messages` / `gen_ai.output.messages`. - Add an "Extraction Span" section to the JavaScript and Python manual instrumentation pages, placed after "Decision Span". The example uses a Clairic invoice extraction (same data as the conventions examples): `gen_ai.extract` op, `extract {model}` name, `gen_ai.operation.name: "extract"`, the request body without `model` as input messages, and the response body without `model` and `usage` as output messages - Add a shared `extraction-span` attributes include: required op/name/operation name, model, provider, and agent attributes, token usage, and the input format (`state`, `fields`, `images`, `reference_date`, `options`, plus field spec types) and output format (`answers`, `truncated`, `span`/`spans` offsets) - JS page links to the Workers AI integration, which creates these spans automatically for Clairic since `@sentry/cloudflare` 11.10.0 Attribute values were checked against sentry-conventions (`model/op/gen_ai.json`, `gen_ai.operation.name`, `gen_ai.input.messages`, `gen_ai.output.messages`), the JS Workers AI instrumentation (`cloudflare.workers_ai` provider name), and the product's extraction parser (spans are recognized by `gen_ai.operation.name`). **Open questions before ready for review** - The field-level message format overlaps with the develop-docs spec in #20107 (still open). Once that merges, should the include link there instead of repeating the field tables? - The existing Decision span docs still show `{type: "evaluation", ...}` wrappers, which the current conventions examples and #20107 drop. Out of scope here, but worth a follow-up. Refs [AGT-3212](https://linear.app/getsentry/issue/AGT-3212/manual-instrumentation-docs-for-extraction-spans) ## 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 @ArthurKnaus. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AD0BQH18P75H%3A1793724768.708079 --> -- [View Session](https://junior-prod.sentry.dev/conversations/slack%3AD0BQH18P75H%3A1793724768.708079) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AD0BQH18P75H%3A1793724768.708079/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Arthur Knaus <7033940+ArthurKnaus@users.noreply.github.com>
…example app (#20391) ## DESCRIBE YOUR PR This removes every docs link to [getsentry/integration-platform-example](https://github.com/getsentry/integration-platform-example), which we're about to archive. The Integration Platform docs now cover the contracts that used to be shown only in that repo; see #20303 (merged) and #20389. **Changes** - `index.mdx`: removed the "Example App" section and its screenshot. - Removed the "We've built an example application…" callout from the top of four pages: `internal-integration.mdx`, `public-integration.mdx`, `webhooks.mdx` and `ui-components/index.mdx`. - Deleted `img/reference-implementation-frontend.png`, which nothing else uses now. The `#example-app` anchor existed only on `index.mdx`, and the only links to it were the callouts this PR removes. I searched the repo and found no other links to it. **Merge order:** merge after #20389, and after the agent-only docs check has passed. Until then, the example is still the only reference for the contracts #20389 adds. **Checks** - Ran `prettier --check` on `index.mdx`, `webhooks.mdx`, `internal-integration.mdx` and `ui-components/index.mdx`. All pass. - Skipped `public-integration.mdx`, which already fails on `master` because of tabs in the JWT snippet. This PR only deletes lines from it. - Didn't check the Vercel preview. ## 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 @mrduncan. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AC0C8Z02BG5Q%3A1793225095.953239 --> -- [View Session](https://junior-prod.sentry.dev/conversations/slack%3AC0C8Z02BG5Q%3A1793225095.953239) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AC0C8Z02BG5Q%3A1793225095.953239/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Matt Duncan <14761+mrduncan@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
… Agent Tracing (#20375) ## DESCRIBE YOUR PR Updates Step 3 of the Sentry Basics content so it explains how Sentry connects telemetry types, and adds Agent Tracing to the feature table. - Renames the header from "Turn On More Features" to "Add context with connected telemetry". - Rewrites the intro to explain that data types share a TraceID (when tracing is enabled) and can be used together, by agents or humans, to investigate an error. - Adds an **Agent Tracing** row under Tracing, linking to `/product/agents/` and the `/product/agents/getting-started/` setup guide. The content lives in `includes/sentry-basics-getting-started.mdx`, which is included on both `/product/sentry-basics/` and `/get-started/`, so the change intentionally shows up on both pages. Prettier also realigned the table column widths, so the other table rows have whitespace-only changes in the diff. ## 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 **steve.zegalia**. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AC0B9ESZ3F9Q%3A1793641060.836229 --> -- [View Session](https://junior-prod.sentry.dev/conversations/slack%3AC0B9ESZ3F9Q%3A1793641060.836229) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AC0B9ESZ3F9Q%3A1793641060.836229/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Steve Zegalia <steve.zegalia@sentry.io>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
## DESCRIBE YOUR PR Adds a short **Plans and Pricing** blurb under the "New to Sentry?" line on [Sentry Basics](https://docs.sentry.io/product/sentry-basics/). It gives an overview of the Developer, Team, Business, and Enterprise plans, how billing and the 14-day trial work, and links to [Pricing & Billing](https://docs.sentry.io/pricing/). The content lives in `includes/sentry-basics-getting-started.mdx`, which `/get-started/` also uses, so the blurb shows up there too. ## 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 **steve.zegalia**. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AC0B9ESZ3F9Q%3A1793641829.320689 --> -- [View Session](https://junior-prod.sentry.dev/conversations/slack%3AC0B9ESZ3F9Q%3A1793641829.320689) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AC0B9ESZ3F9Q%3A1793641829.320689/?project=4510944073809921) <!-- junior-session-footer:end --> --------- Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Steve Zegalia <steve.zegalia@sentry.io> Co-authored-by: Shannon Anahata <shannon.anahata@gmail.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Please update the IS YOUR CHANGE URGENT? section of the PR description:
This information helps the Docs team prioritize your review. |
|
Getting ready to monitor this change · Rollout details
|
## DESCRIBE YOUR PR The Unreal SDK adds an option to choose which views the Sentry Crash Reporter shows and in which tab order. Adds a "Views" item to the list of appearance settings on the Sentry Crash Reporter page. It explains that the crash reporter opens the first listed view that has data, that each view can be added only once, and that an empty list shows all views in the default order. Not ready to merge until the Unreal SDK bundles a crash reporter version that supports this option. ## Related Items - getsentry/sentry-unreal#1687 - getsentry/sentry-desktop-crash-reporter#309 ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs)
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit cf04aa3. Configure here.
| .join('\n'); | ||
| } | ||
|
|
||
| function frontmatterLines(title: string, requestedPath: string): string[] { |
There was a problem hiding this comment.
Suggestions include synthetic missing pages
Medium Severity
renderSiblingList still emits .md links for every child, including synthetic missing doctree nodes. The new exact-path check treats those nodes as unknown paths, so the helper can recommend pages that this same route will answer with Page Not Found. Agents following those suggestions take a dead-end hop instead of reaching a real export.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit cf04aa3. Configure here.
…base branches (#3153) In getsentry/sentry-docs, a scheduled automation opened the weekly sync PR getsentry/sentry-docs#20685 (`master` → `java-v9`) while the long-lived collection PR getsentry/sentry-docs#19963 (`java-v9` → `master`) was open. `github_createPullRequest` treated #19963 as the PR below the sync PR. The stack walk then went `java-v9` → `master` → `java-v9`, found the sync PR again at each step, and ran until `MAX_STACK_DEPTH`. It created stack 20686, which lists both PRs again and again. When the sync PR merged, GitHub retargeted #19963 onto `java-v9`, its own head, and marked it merged. `master` did not change, but the collection PR had to be opened again (getsentry/sentry-docs#20718). Changes in `stackGitHubPullRequest`: - Do not stack a PR whose head is the default branch. A sync from the trunk is not stacked work. - Stop the walk at the default branch. - Do not stack when the walk reaches a PR that is already in the chain. The GitHub plugin docs now list these cases. Open question: a PR into a long-lived integration branch, such as `feat/x` → `java-v9`, still stacks on the collection PR (`java-v9` → `master`). If someone merges that stack as one group, the collection branch could land on the trunk early. A fix probably needs a rule for when the PR below is a long-lived branch, for example a draft PR, so this PR does not change it. <!-- junior-request-attribution:start --> via **alexander.dinauer**. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AC089VFRB8N9%3A1794375474.875259 --> -- [View Session](https://junior-prod.sentry.dev/conversations/slack%3AC089VFRB8N9%3A1794375474.875259) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AC089VFRB8N9%3A1794375474.875259/?project=4510944073809921) <!-- junior-session-footer:end --> --------- Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Alexander Dinauer <alexander.dinauer@sentry.io> Co-authored-by: Thomas Jiang <20501235+thomasjiangcy@users.noreply.github.com>


Weekly automated sync of
masterintojava-v9.Brings in 212 commits from
master.Please merge with a merge commit (not squash) after review.
via automation
sched_ad73d0ab6d1d56c93807b4c35dcc4acd· Run IDsched_ad73d0ab6d1d56c93807b4c35dcc4acd:1794299400000.--
View Session [Sentry]