Repository navigation
Bump API schema to e8dba7a5 - #20144
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 reference page loads, API 404 share, and API page errors. An issue escalates when API 404 share rises or those page errors rise. API reference page loads that collapse also escalate. Services: Mention PlanWhat changedThe build pins the API schema to SHA e8dba7a51eb02705ffc062baf3f581856f6c684e. API reference pages still render from openapi-derefed.json at that pin. That OpenAPI file did not change from the prior pin. Only rpc_method_schema.json changed in the schema repo. This site does not fetch rpc_method_schema.json. sentry-docs must deploy before the pin is live on API reference pages. develop-docs also rebuilds this shared src file from the same commit. Catalog and Vercel deploy mapping name both ships. API reference pages are generated only for sentry-docs. RiskA schema that drops or renames endpoint slugs breaks old API reference links. Readers then get 404 pages on those paths. A bad fetch or parse can fail the sentry-docs production build. The same src file ships in develop-docs. A compile failure can fail that production ship as well. Intended effectThis pin does not change the OpenAPI file the site fetches. No new API reference content is queryable. The live evidence is that API reference pages still load after deploy. Expected shift is none. Hold the pooled 24h load rate. Absent looks like that load rate falling below the band while other pages still load.
Prior 24h was 792 loads. Last 24h was 789 loads. Those map to 33 and 33 loads per hour. Regression watchThis pin can break API reference paths if slugs change. Render can also throw on those pages if the schema fails. Watch 404 share and error share on that same path. If 404 share rises, inspect renamed endpoint slugs.
Prior 24h had 8 API 404s and 9 API page errors on 792 loads. Last 24h had 13 API 404s and 15 API page errors on 789 loads. Last 24h 404s were mostly path api/alerts. Not observableNo runtime metric records the schema SHA. The 48h /api/ pageload trace query timed out, so prior-day p95 is missing. Last 24h p95 was 6.4s on 477 pageload spans, and traces are sampled at 30%. develop-docs does not generate API reference pages from this schema, so that ship has no pre-ship rate on the changed path. |
No description provided.