Repository navigation
docs(organization): Add steps for switching SaaS data storage location - #20151
Conversation
Co-Authored-By: Paul Jaffré <paul.jaffre@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
…ions Co-Authored-By: Paul Jaffré <paul.jaffre@sentry.io>
Co-Authored-By: Paul Jaffré <paul.jaffre@sentry.io>
Co-Authored-By: Paul Jaffré <paul.jaffre@sentry.io>
Co-Authored-By: Paul Jaffré <paul.jaffre@sentry.io>
|
The plan checks pageload volume on the storage-location guide, pageload duration, and client errors on that URL. An issue escalates when pageload volume falls or those errors rise. Monitoring in Services: Mention PlanWhat changedReaders of the Data Storage Location page now see a Planning a switch expandable. The expandable lists SaaS steps to create a new organization and update DSNs. sentry-docs must deploy before this copy is live. The deploy workflow maps Vercel Production sentry-docs to this service. RiskA broken MDX render or Expandable hydrate can blank that page for readers. New links can send readers to missing organization, integration, or pricing pages. Wrong SSO or integration steps can make customers remove working tools too soon. That guidance error has no runtime signal. Intended effectThis change is new documentation. Sentry does not record that the checklist appeared. Absent looks the same as confirmed in Sentry. Both show only that the page still loads. Do not treat pageload volume as proof the new copy shipped. Regression watchFilter production with
If error events rise, inspect titles for Expandable hydrate failures on this path. Not observablePlausible event Open Expandable with title Planning a switch is not connected. That event would show readers opened the new checklist. Pageload spans on this URL did not return HTTP status codes, so 4xx and 5xx on the page are unknown. Click-through 404s on the new links are not split from other traffic. |
DESCRIBE YOUR PR
The Data Storage Location page tells SaaS customers that the only way to switch between US and EU is to create a new organization, but it doesn't explain what that involves. Customers who switched regions told us they had to work it out on their own.
This adds a short, user-led checklist under Switching Data Storage Locations for Existing Organizations > SaaS. It covers what stays behind, recreating the setup in the new org, updating DSNs, tokens, and API domains, checking the new org, and retiring the old one. It doesn't suggest that Sentry moves data between SaaS orgs.
Before merging, an SME should confirm the integration and SSO guidance, especially whether any integrations need to be uninstalled from the old org first. Prettier also normalized whitespace in the existing storage location table.
IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST
via paul.jaffre.
--
View Junior Session [Sentry]