Every project you integrate with Sentry, and every SDK that you set up has one common bit: the Data Source Name , or in short DSN. It tells the SDK where to find the Sentry server, how to authenticate and which Sentry project to associate your events with.
In an ongoing effort to improve our quality of service, we are extending DSNs with a distinct subdomain for your organization. The new domain name always follows this schema:
The new DSNs compare like this:
Old DSN: https://<key>@sentry.io/4711 New DSN: https://<key>@o42.ingest.sentry.io/4711
When you set up a new project or retrieve an existing DSN, you will see that project settings now shows the new DSN including the subdomain:
Additionally, our documentation pages conveniently display the updated DSN when logged in with your Sentry Account:
What do YOU have to consider?
There is absolutely no action required on your end.
The DSNs you have configured in your existing applications will stay valid. Our servers still operate on the same ip ranges as before. Simply use the new DSNs for any application that you set up for Sentry. Of course, you are free to update existing applications with the new DSNs.
If you have any questions or need help, we have many ways to provide support.