Repository navigation
Bump API schema to 81f843cd - #20176
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Please update the IS YOUR CHANGE URGENT? section of the PR description:
This information helps the Docs team prioritize your review. |
|
The plan checks API page loads, API 404s, and error events on those pages. An issue escalates when API 404s rise or those error events increase. Services: PlanWhat changedAPI reference pages now build from OpenAPI schema 81f843cd. GitHub compare shows no OpenAPI JSON change from pin 4973d6c8. Endpoint pages likely match the prior pin. sentry-docs must deploy before the new pin is live. develop-docs also ships this commit from the same repo. develop-docs does not render these API reference pages. RiskA bad schema pin can omit API pages or rename endpoint slugs. Readers then see 404s on former API URLs. A fetch failure at build time blocks the sentry-docs deploy. The shared resolver module also ships on develop-docs. Intended effectAPI pages generated from the schema keep loading. Confirm this on Sentry project docs. Do not use project develop-docs for this signal. After a develop-docs-only deploy, mark intended effect unknown. The schema JSON did not change. Do not expect new pages. Absent looks like the API load share falling toward 0 while all page loads hold. Last 24h API loads were 852 of 18682. Prior 24h API loads were 786 of 17310. About 398 of the 852 API loads lack api_category and are MDX, not schema pages. Escalate if a named api_category slice falls to 0 while total API loads hold.
Regression watchA wrong pin 404s former API URLs first. The catch-all page imports the resolver, so a module failure can raise errors on all docs pages. develop-docs ships the same module. Existing API 404s already concentrate on api/alerts, api/organizations, and api/events. Treat a rise above the measured share as a regression. Do not treat those existing 404s as new.
Last 24h API 404s were 16 against 852 API page loads. Last 24h API-URL errors were 8. Prior 24h API-URL errors were 8 against 786 API page loads. Last 24h docs errors were 241 against 18682 page loads. Prior 24h docs errors were 207 against 17310 page loads. Last 24h develop-docs errors were 32 against 1892 page loads. Prior 24h develop-docs errors were 29 against 1655 page loads. Not observableThe prior-day count for docs.page.not_found on api paths did not return. That 404 share uses one 24h window only. Pageload traces with transaction:/api/* returned 0, so this plan does not use span failure rate for API pages. |
|
Verified in
|
No description provided.