[sentry-api-schema-updater]

No description provided.

[vercel]

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

Project	Deployment	Actions	Updated
develop-docs	Ready	Preview	Oct 16, 2026 8:38pm UTC
sentry-docs	Ready	Preview	Oct 16, 2026 8:38pm UTC

[github-actions]

Please update the IS YOUR CHANGE URGENT? section of the PR description:

• Select exactly one option.
• If you selected an urgent or other deadline, provide the date as YYYY-MM-DD.

This information helps the Docs team prioritize your review.

[cursor]

The plan checks API reference page loads, API 404s, and catch-all page errors. It also checks API pageload time. An issue escalates when API 404s rise or those errors rise.

Services: sentry-docs.

Mention @change-monitor in a comment to update the plan.

Plan

What changed

The docs build now fetches the OpenAPI schema from SHA fc470a5b. API reference pages rebuild from that schema. Schema release 0.360.3 only changes the schema-repo release bot. The OpenAPI document itself did not change. This change is live after sentry-docs deploys. develop-docs rebuilds the same commit. It does not generate those API pages.

Risk

A bad schema fetch fails the sentry-docs build. A schema that drops paths makes API pages return 404. Bad endpoint markdown can throw on the catch-all page. Other docs pages share that page module.

Intended effect

The pin publishes the same API pages. Confirmed means the API page-load share holds near the band. Absent means that share falls toward zero while other page types still load.

Signal	Baseline	Window	Rule	Source
API share of docs.page.load (page_type:api / all page_type, production)	4.6-4.8% (913 of 19859, then 763 of 15817)	2026-10-14T20:34:00Z to 2026-10-15T20:34:00Z and 2026-10-15T20:34:00Z to 2026-10-16T20:34:00Z	Hold near this band. Do not treat the band edge as absent.	Sentry org sentry project docs, metric docs.page.load, environment:production

Regression watch

A dropped or unparsable schema makes /api/ paths 404. Render failures show on the catch-all route. Slow or broken API pages show in pageload time.

Signal	Baseline	Window	Rule	Source
API 404 share (docs.page.not_found requested_path:api* / API docs.page.load)	0.4-1.1% (4/913, then 8/763)	2026-10-14T20:34:00Z to 2026-10-15T20:34:00Z and 2026-10-15T20:34:00Z to 2026-10-16T20:34:00Z	Do not rise above this band. Split by requested_path if the share jumps.	Sentry org sentry project docs, metric docs.page.not_found, environment:production
Catch-all error share (error events on /:path*? / all docs.page.load)	0.67-1.35% (268 of 19859, then 106 of 15817). This rate may move day to day.	2026-10-14T20:34:00Z to 2026-10-15T20:34:00Z and 2026-10-15T20:34:00Z to 2026-10-16T20:34:00Z	Do not rise above this band.	Sentry org sentry project docs, dataset errors, environment:production, transaction /:path*?
API pageload p95 (span.op:pageload, url.path:/api/*)	8.3-9.8s (2d pooled 8261ms, last 24h 9817ms). Agent traffic may dominate this p95.	2026-10-14T20:34:00Z to 2026-10-16T20:34:00Z and 2026-10-15T20:34:00Z to 2026-10-16T20:34:00Z	Hold near this band.	Sentry org sentry project docs, traces, environment:production

If API 404s rise, inspect which requested_path jumped. If catch-all errors rise, inspect failures during API page MDX render.

Not observable

The schema SHA is not in runtime telemetry. Error events do not split API pages from other catch-all routes. User-only API pageload traces returned zero rows. Error logs that match api in the message are too broad to use.