A recent update/PR was made to sentry config in the various BE services. This was an attempt to fix an issue where containers wouldn’t start up properly for some BE services due to sentry config having an incorrect null value.
The problem with the fix is that with sentry working properly in dev & test, it consumes all of the budget due to all the errors in dev/test.
We will need to revert the sentry changes made in the referenced PR and ensure that sentry_dsn populates with an empty string(null value seems to cause issues with containers not being able to start up properly).
TODOs
[x] Revert changes made in previous PR. Probably ideal to just test one BE service first before doing all.
[x] Make necessary updates to 1pass where sentry_dsn is null for a given BE service
[x] Verify BE services are running properly when rolled out to dev
A recent update/PR was made to sentry config in the various BE services. This was an attempt to fix an issue where containers wouldn’t start up properly for some BE services due to sentry config having an incorrect null value.
The problem with the fix is that with sentry working properly in dev & test, it consumes all of the budget due to all the errors in dev/test.
We will need to revert the sentry changes made in the referenced PR and ensure that
sentry_dsn
populates with an empty string(null value seems to cause issues with containers not being able to start up properly).TODOs
sentry_dsn
is null for a given BE service