Integrate sentry (Opt-in, disabled by default)

[etiennedi]

Changes

• Optional Sentry support. This is disabled by default. No behavior changes unless Sentry is explicitly activated
• Right now any caught panic, i.e. all places where we call recover() will also send the panic to Sentry if enabled
• Non-panic errors are not yet tracked. Here we need to gain some experience of what errors are worth tracking.

Configuration

Env var	Default	Notes
SENTRY_ENABLED	false	Overall feature gate. If false, no sentry code will ever be executed.
SENTRY_DSN	""	Connection string as defined in the Sentry UI. Required if SENTRY_ENABLED=true
SENTRY_DEBUG	false	Passed directly to Sentry init func
SENTRY_RELEASE	""	Sentry tries to figure out the release on its own, but this will likely not work in Docker. Ideally, here we use K8s magic to always automatically set this to the image tag
SENTRY_TAG_<key>	""	Set arbitrary key/value pairs, such as SENTRY_TAG_foo=bar . Must adhere to Sentry tag rules wrt length and allowed chars.

Review checklist

• Documentation has been updated, if necessary. Link to changed documentation:
• Chaos pipeline run or not necessary. Link to pipeline:
• All new code is covered by tests where it is reasonable.
• Performance tests have been run or not necessary.

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud