[EXP-35-236] sentry release tracking + custom tags #236
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We can activate now sentry release tracking by passing a
SENTRY_RELEASE
env like so:export SENTRY_RELEASE=$(git rev-parse --short HEAD)
https://docs.sentry.io/product/releases/
if this is set to a value sentry will show it under the Releases section which can be further filtered by the environment.
The environment (previously
ENV
) has been replaced in favor of sentry's defaultSENTRY_ENVIRONMENT
https://docs.sentry.io/platforms/python/configuration/options/#common-options
Also changed some custom tags like discussed with Bob.