To help our customers meet changing privacy and compliance requirements, we’re investing in infrastructure that supports data residency. This will provide companies that need to store PII outside of the US with access to contextual data (ie. a user who experienced the issue) by storing it regionally so they can resolve issues faster.
To help deliver the best experience, we will be changing the front-end URLs of our service from their old format (sentry.io/organizations/acme), to the new format (acme.sentry.io).
Yes, requests to the old URLs will automatically be redirected to the new ones.
We recommend you update your bookmarks, allow-lists, and any custom scripts that rely on static URLs.
Sentry integrations will not be affected by this change.
An organization slug is a unique, short, lowercased name consisting of letters, numbers, and hyphens.
It is sometimes derived from the organization name.
A Quick Brown Fox may have an associated slug:
An organization slug should consist of letters, numbers, and or hyphens. For example:
The organization slug may not begin, nor end with hyphens.
In addition to changing your organization’s slug name, there are a few additional things you might want to update:
For integrations like Jira, GitHub, Slack etc any old links that use your organization slug to link you back into your Sentry account won’t be redirected. If you would like to update them, please review our integration troubleshooting guide to identify and update any integration configuration values that references the organization slug, and update them accordingly.
If you are using sentry-cli you will also have to update the
SENTRY_ORG environment variable. Refer to the documentation for more details on this configuration value.
If your organization is using SCIM/SAML, you will need to update the SCIM/SAML configuration values for the provider you’re using. Refer to the SCIM/SAML documentation here.
If you are using any of our public API URLs, you will need to update the organization slug in URLs as appropriate.