Closed MrLokans closed 7 years ago
Perhaps we could have checked the presence of the DSN setting in the configuration file and if it is missing warn the user about the misconfiguration once and do not call raven client methods
You can set the value of the DSN to None
, i.e.
# config.yaml
SENTRY:
DSN: null
See the test here -- https://github.com/mattbennett/nameko-sentry/blob/v0.0.3/test_nameko_sentry.py#L109-L118
I see your PR though and agree that we should also cope with a config file that was missing the SENTRY
section completely. Thank for the contribution :)
I think this has been handled already.
Hello there. I have a case when I have a set of configs to be used in different environments (e.g. dev/prod) and I don't want any sentry error handling in the development environment, but if I simply do not fill the required settings in the config - my service will fail to be loaded failing with the following error:
So what is the correct way to enable the Sentry logging only on the specific environemnt? Thank you