🐛 Sentry alerts showing as environment dev

[mitchdawson1982]

Describe the bug.

NOTE: Labelled as a bug however it appears that conflicting Sentry code within the Datahub Telemetry module could be the root cause

Sentry Issue

We have a Django application running across three environments (test, dev and preprod), each environment has an ENV variable configured with the respective value. This variable is used as the environment argument in the sdk init.

We noticed that events were being received in Sentry with an environment of dev only, i.e. test or preprod were never used despite being configured correctly. When validating this behaviour locally I have also found that periodically alerts will come in with the environment as dev despite an entirely different value being provided. I have further noticed that when this occurs, the release value is also different from a working example.

To Reproduce

visit https://data-platform-find-moj-data-dev.apps.live.cloud-platform.service.justice.gov.uk/sentry-debug/ to generate a divide by zero exception.

Expected Behaviour

Expected Result
When ENV=new-env1 received alerts should show the environment as new-env1

Additional context

It appears that the datahub telemetry code is invoking sentry here which could explain our issues.

Proposed work around

• Unset SENTRY_DSN environment variable across environments
• Define a new variable to hold the sentry dsn value i.e. SENTRY_DSN_WORKAROUND
• Deploy and validate correct Sentry operation across environments