Releases & Health
A release is a version of your code that is deployed to an environment. When you give Sentry information about your releases, you can:
- Determine issues and regressions introduced in a new release
- Predict which commit caused an issue and who is likely responsible
- Resolve issues by including the issue number in your commit message
- Receive email notifications when your code gets deployed
Include a release ID (often called a "version") when you configure your client SDK. This ID is commonly a git SHA or a custom version number.
The release name cannot:
- contain newlines, tabulator characters, forward slashes(
/) or back slashes(
- be (in their entirety) period (
.), double period (
..), or space (
- exceed 200 characters
Releases are global per organization; prefix them with something project-specific for easy differentiation.
using Sentry; // Add this to the SDK initialization callback options.Release = "firstname.lastname@example.org";
The SDK attempts to locate the release to add to events sent to Sentry.
The SDK will first look at the entry assembly's
AssemblyInformationalVersionAttribute, which accepts a string as
value and is often used to set a GIT commit hash.
If that returns null, it'll look at the default
AssemblyVersionAttribute which accepts the numeric version number. When creating a project with Visual Studio, the value is set to 220.127.116.11.
Since that usually means that the version is either not being set, or is set via a different method. The automatic version detection will disregard this value and no Release will be reported automatically.
How you make the version available to your code is up to you. For example, you could use an environment variable that is set during the build process.
This tags each event with the release value. We recommend that you tell Sentry about a new release before deploying it, as this will unlock a few more features as discussed in our documentation about releases. But if you don’t, Sentry will automatically create a release entity in the system the first time it sees an event with that release ID.
After configuring your SDK, you can install a repository integration or manually supply Sentry with your own commit metadata. Read our documentation about setting up releases for further information about integrations, associating commits, and telling Sentry when deploying releases.