[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 22, 2026 3:28pm UTC
sentry-docs	Ready	Preview	Oct 22, 2026 3:28pm 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 page loads, API 404s, and client errors on API pages. An issue escalates when API 404s or those client errors rise. The new Integrations endpoint page should start to record loads after ship.

Monitoring in production

Services: sentry-docs.

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

Plan

What changed

The API reference now documents List Stack Trace Directory Prefixes for Code Mapping Autocomplete. Requests to /api/integrations/list-stack-trace-directory-prefixes-for-code-mapping-autocomplete/ should return that page. Other API slugs stay the same. This change is live after a sentry-docs deploy. develop-docs shares the source file but does not generate these API pages.

Risk

A bad schema can 404 existing API URLs or crash API page render. The blast radius is the /api/ reference tree. The Integrations category is the slice that this endpoint joins.

Intended effect

The new endpoint page must record page loads. absent is a zero count on that page while Integrations 404s rise. Sibling Integrations loads with no new 404s and a zero count stay unknown. Visitors may not open the new URL.

Signal	Baseline	Band	Window	Rule	Source
docs.page.load for api_endpoint list-stack-trace-directory-prefixes-for-code-mapping-autocomplete	0	0	2026-10-21T15:22:00Z to 2026-10-22T15:22:00Z	rise above 0	Sentry org sentry project docs. api_endpoint:list-stack-trace-directory-prefixes-for-code-mapping-autocomplete environment:production sum of docs.page.load

Regression watch

A schema fault shows first as more API 404s or more client errors on API pages. Watch the Integrations slice because that category gained the new page. Pair each 404 and error count with API page loads in the same window.

Signal	Baseline	Band	Window	Rule	Source
API 404 rate. docs.page.not_found with requested_path api* over docs.page.load with page_type api	18 404s and 866 page loads in the last 24h. 15 404s and 772 page loads in the prior 24h	1.9-2.1%	last 24h 2026-10-21T15:22:00Z to 2026-10-22T15:22:00Z. prior 24h 2026-10-20T15:22:00Z to 2026-10-21T15:22:00Z	hold in band	Sentry org sentry project docs. 404s requested_path:api* environment:production sum of docs.page.not_found. loads page_type:api environment:production sum of docs.page.load
Integrations 404s. docs.page.not_found with requested_path api/integrations	1 in 48h	0-1 per 24h	2026-10-20T15:22:00Z to 2026-10-22T15:22:00Z	hold in band	Sentry org sentry project docs. requested_path:api/integrations environment:production sum of docs.page.not_found
Client error rate on API pages over API page loads	4 errors and 866 page loads in the last 24h. 17 errors and 1638 page loads in the last 48h	0.46-1.0%	last 24h 2026-10-21T15:22:00Z to 2026-10-22T15:22:00Z. last 48h 2026-10-20T15:22:00Z to 2026-10-22T15:22:00Z	hold in band	Sentry org sentry project docs. errors environment:production url:*/api/* count. The 48h search used http.url. loads as above
Integrations page-load share of API page loads	23 of 866 in the last 24h. 11 of 772 in the prior 24h	1.4-2.7%	last 24h 2026-10-21T15:22:00Z to 2026-10-22T15:22:00Z. prior 24h 2026-10-20T15:22:00Z to 2026-10-21T15:22:00Z	hold in band	Sentry org sentry project docs. page_type:api api_category:integrations environment:production sum of docs.page.load over all API page loads

Most recent API client errors are Algolia fetch failures and promise rejections. Treat a new render error on /api/ as a regression even inside the rate band.

Not observable

No probe requests the new URL. A zero load count after ship can mean no visitors. The 24h and 48h error searches used different URL fields. Pageload traces for /api/ are not used. The URL filter may include unrelated /api/ spans.

[cursor]

Verified in production

• The new Integrations endpoint page recorded a load, and API 404s stayed low.