Data Source Name (DSN)

Learn about Sentry's Data Source Name structure and use.

Sentry automatically assigns you a Data Source Name (DSN) when you create a project to start monitoring events in your app.

A DSN tells a Sentry SDK where to send events so the events are associated with the correct project.

If this value is not provided, SDKs will try to read it from the SENTRY_DSN environment variable, where applicable. This fallback does not apply in cases like a web browser, where the concept of environment variables does not exist.

If an SDK is not initialized or if it is initialized with an empty DSN, the SDK will not send any data over the network, such as captured exceptions.

DSNs are safe to keep public because they only allow submission of new events and related event data; they do not allow read access to any information.

While there is a risk of abusing a DSN, where any user can send events to your organization with any information they want, this is a rare occurrence. Sentry provides controls to block IPs and similar concerns. You can also rotate (and revoke) DSNs by navigating to [Project] > Settings > Client Keys (DSN).

If your application is shipped to client devices, if possible, we recommend having a way to configure the DSN dynamically. In an ideal scenario, you can "ship" a new DSN to your application without the customer downloading the latest version. We recognize that this may not always be practical, but we cannot offer further advice as this scenario is implementation specific.

If you're in the process of setting up a project, you can find your DSN in the installation or configuration code snippets provided in during setup:

DSN in code snippet

You can also find the DSN in your project settings by navigating to [Project] > Settings > Client Keys (DSN) in

The DSN configures the protocol, public key, server address, and project identifier. It is composed of the following parts:


For example:

Sentry.init({ dsn: "" });

Has the following settings:

The secret part of the DSN is optional and effectively deprecated. While clients will still honor it, if supplied, future versions of Sentry will entirely ignore it.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").