LOGENTRIES_TOKEN spam during init #9
Assignees
Comments
|
We should change logentries.py and base.py to omit any configuration at all if no token is available. |
mrmachine
added a commit
that referenced
this issue
Mar 6, 2018
* Only configure logentries and add `logentries` handler to the root
logger if `LOGENTRIES_TOKEN` environment variable is specified.
* Rename `logfile` formatter to `default`, because we don't only use it
with the `logfile` handler.
* Remove `require_debug_true` filter from console handler.
* Remove `level` from `console` and `logfile` handlers. Instead, allow
Python to inherit from the parent logger.
* Add a `null` handler. Silence noisy loggers with the `NULL_LOGGERS`
environment variable (space separated logger names). For example:
`NULL_LOGGERS=foo bar.baz`.
* Use `LOGLEVEL` environment variable (default: `INFO`) in the root logger.
* Enable `logfile` handler in the root logger.
* Allow log level overrides via `{LEVEL}_LOGGERS` environment variables.
For example: `WARNING_LOGGERS=foo`, `DEBUG_LOGGERS=bar.baz abc`.
Recognised levels are: `EXCEPTION`, `ERROR`, `WARNING`, `INFO`, `DEBUG`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The above appears during boot (twice in dev envs), and seems to have no effect. Can we suppress it if
DEBUG == True?The text was updated successfully, but these errors were encountered: