Default to a blank dsn if sentry env vars are not set #4963
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.
✨ Description of Change
Link to GitHub issue or Jira ticket: N/A
Description: Currently we see the following warning during startup when local testing:
10:13:50,850 |-WARN in io.sentry.logback.SentryAppender[sentry] - Failed to init Sentry during appender initialization: DSN is required. Use empty string or set enabled to false in SentryOptions to disable SDK.
This also causes logback to dump a whole bunch of other debug logs.
The fix sets a default value of empty string (which disables Sentry) for the dsn if the SENTRY_DSN_BACKEND or SENTRY_DSN environment variables are not set.