Repository navigation
Bump API schema to 3f13c2e8 - #19842
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 not-found counts, and client errors on those pages. An issue escalates when API page loads fall or those errors rise. Monitoring in Services: Mention PlanWhat changedAPI reference pages now rebuild from OpenAPI schema 3f13c2e8. Those pages no longer document a byteSize field beside eventCount. sentry-docs must deploy before this content is live. develop-docs also rebuilds this source file. Developer docs do not serve API reference pages. RiskA bad schema can break API page render. Users then see a 404 or a client error. The blast radius is every API reference page that uses the same renderer. The byteSize drop should not change routes. Intended effectAPI reference pages keep loading after the new schema ships. That shows the rebuilt pages serve traffic. Absent looks like API page loads drop toward zero while other page loads hold. Telemetry cannot show that byteSize left the HTML.
Regression watchThis change can break API page render. It can also 404 a page if a slug disappears. The field drop should not remove routes. Algolia and kapa fetch failures already appear on these pages. Treat a new error title or a rise in the h6 TypeError as a regression.
Not observableWhether byteSize left the rendered HTML. Pageload traces do not use /api/ in the transaction name. develop-docs has no API reference page signal. |
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
No description provided.