[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	Building	Preview	Oct 22, 2026 5:32pm UTC
sentry-docs	Building	Preview	Oct 22, 2026 5:32pm 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 path 404s, and errors on those pages. An issue escalates when the 404 share or the error share rises. Published endpoint pages should match the prior schema.

Rollout complete

Services: sentry-docs.

Plan

What changed

API reference pages now build from OpenAPI schema SHA 1f67a23bb90f0e17e8146b81fbf52c154a7dacfd. That commit did not change the deref schema file. Endpoint pages should match the prior SHA. sentry-docs must deploy before this change is live. develop-docs shares this source file but does not generate OpenAPI pages.

Risk

A missing or invalid schema at the new SHA drops API pages from the static build. Readers then see 404s on former endpoint URLs. A malformed schema can throw during API page render. The blast reaches every API reference page.

Intended effect

API pages keep loading at the pre-ship rate. The deref schema did not change, so the expected shift is a hold. Absent looks like docs.page.load with page_type:api falling toward zero while other page types keep traffic.

Signal	Baseline	Rule	Source
docs.page.load with page_type:api	0.54-0.61 loads per minute. Last 24h sum 865. Prior 24h sum 785. Pooled rate 0.57 per minute.	Hold the pooled rate inside the band.	Sentry org sentry, project docs, environment production. Query metric.name:docs.page.load AND page_type:api AND sentry.environment:production. Window 2026-10-20T17:33:35Z to 2026-10-22T17:33:35Z.

Regression watch

A bad schema can 404 former endpoint URLs or throw on API pages. Some API 404s already occur from bad paths. Use share of API page loads, not a hold at zero. The 404 share may vary by day.

Signal	Baseline	Rule	Source
docs.page.not_found with requested_path:api* as a share of API page loads	0.9-2.3%. Last 24h 20 not-found vs 865 loads. Prior 24h 7 vs 785.	Stay in band. Escalate if the share rises above 2.3%.	Sentry org sentry, project docs, environment production. Query metric.name:docs.page.not_found AND requested_path:api* AND sentry.environment:production. Denominator is docs.page.load with page_type:api. Window 2026-10-20T17:33:35Z to 2026-10-22T17:33:35Z.
Error events with url:*/api/* as a share of API page loads	0.6-1.9%. Last 24h 5 errors vs 865 loads. Prior 24h 15 vs 785.	Stay in band. Escalate if the share rises above 1.9%.	Sentry org sentry, project docs, environment production. Query environment:production url:"*/api/*". Denominator is docs.page.load with page_type:api. Window 2026-10-20T17:33:35Z to 2026-10-22T17:33:35Z.

Not observable

Document transaction p95 on url.path:/api/* was 7.0 s in the last 24 h. The prior day was not measured, so no latency band is set. No served-page signal exposes the schema SHA. The deref schema file did not change, so no new-endpoint counter exists.

[cursor]

Verified in production

• API reference pages still load after this ship.