docs(integrations): Remove obsolete Vanta EU guide

[sansynx]

DESCRIBE YOUR PR

Removes the separate Vanta EU guide and its entries from the integration lists. The old guide URL and both legacy URLs redirect directly to the existing Vanta guide, so saved links still work.

Vanta's Sentry setup guide uses the Vanta app. Its regional guidance says integration setup is the same across regions. This change only removes the duplicate documentation, not support for EU customers.

Fixes #19757

IS YOUR CHANGE URGENT?

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: Not urgent, can wait up to 1 week+

PRE-MERGE CHECKLIST

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

[vercel]

@sansynx is attempting to deploy a commit to the Sentry Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[cursor]

The plan checks whether old Vanta EU URLs 404, whether client errors rise, and whether page-not-found volume holds. An issue escalates when compliance 404s appear or client errors rise above the measured band.

Services: sentry-docs, develop-docs.

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

Plan

What changed

Requests to the old Vanta EU guide URLs now redirect to the existing Vanta guide. The Vanta EU page is removed from the compliance and integrations lists. Saved links to /integrations/compliance/vanta-eu/, /integrations/vanta-eu/, and /organization/integrations/vanta-eu/ should land on /integrations/compliance/vanta/.

sentry-docs must deploy before user docs show this. middleware.ts also ships on develop-docs, which drops the old developer-docs redirect for /organization/integrations/vanta-eu/.

Risk

If the new redirects miss, saved links return 404 instead of the Vanta guide. Anyone with an old Vanta EU URL is affected. A middleware mistake can also break other exact-match docs redirects on both docs sites.

Intended effect

Old Vanta EU URLs should redirect to the Vanta guide. Sampled pageload and navigation spans for /integrations/compliance/vanta-eu/ and /integrations/compliance/vanta/ were 0 over 7 days, so traces cannot confirm the new redirect. Absent looks the same: those transaction counts stay at 0.

Vanta-related middleware spans still show people request Vanta URLs. That volume is not a success signal. Middleware runs for 404s too.

Signal	Baseline	Rule	Source
Pageload or navigation spans for transaction:/integrations/compliance/vanta/ in production	0 spans in 7d, window 2026-10-01T16:19:00Z to 2026-10-08T16:19:00Z	A rise above 0 confirms the destination is reached. Staying at 0 is absent. Traces sample at 30%.	Sentry org sentry project docs, query environment:production transaction:"/integrations/compliance/vanta/" (span.op:pageload OR span.op:navigation)

Regression watch

If the redirects miss, the not-found page records docs.page.not_found with requested_path of integrations/compliance. That counter is 0 today. A rise means old Vanta EU URLs 404. Client errors are the symptom-class watch for a middleware fault.

Signal	Baseline	Rule	Source
docs.page.not_found for requested_path:integrations/compliance in production	0 events in 7d, window 2026-10-01T16:19:00Z to 2026-10-08T16:19:00Z	Stay at 0. Any rise is a regression on the changed path.	Sentry org sentry project docs, query metric.name:docs.page.not_found AND environment:production AND requested_path:integrations/compliance
docs.page.not_found total versus docs.page.load in production	492 not-found events and 20131 page loads in 24h, window 2026-10-07T16:19:00Z to 2026-10-08T16:19:00Z, rate 2.4%	Hold near 2.4%. Escalate if not-found volume rises while page loads hold.	Sentry org sentry project docs, queries metric.name:docs.page.not_found AND environment:production and metric.name:docs.page.load AND environment:production
Client error events in production	98 events in 24h, window 2026-10-07T16:19:00Z to 2026-10-08T16:19:00Z. Hours 10:00-16:00 UTC on 2026-10-08 showed 3-12 errors per hour	Hold in the 3-12 errors/hour band. Escalate if hourly errors stay above 12.	Sentry org sentry project docs, query environment:production on error events

If compliance 404s rise, check logs for requests to /integrations/compliance/vanta-eu/ that did not 308.

Not observable

Per-URL redirect status is not in traces. Grouping middleware spans by http.url for vanta-eu returned no rows, so the 2300 Vanta-related middleware spans over 7 days cannot be split between the old path and the Vanta guide. The listing-page edit has no telemetry. develop-docs had 0 Vanta spans in 7 days, so the dropped developer-docs redirect is not observable.