You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed with @mbenadda [1] some relevant logs may get lost if we only use sentry for logs with a level >= WARNING.
Proposal
Add a new logger using the console handler with the INFO level so that we can store and use them at a system level depending on the infrastructure (e.g. OpenShift + ELK).
As discussed today from Slack with @jmaupetit and @mbenadda , it seems log ouptut is totally muted in local development, particularly from CLI commands like bootstrap_elasticsearch.
This would be nice to have logger config for local development to have logger correctly enabled so we can use logger.info() and even logger.debug() inside commands.
Purpose
As discussed with @mbenadda [1] some relevant logs may get lost if we only use sentry for logs with a level
>= WARNING
.Proposal
Add a new logger using the
console
handler with theINFO
level so that we can store and use them at a system level depending on the infrastructure (e.g. OpenShift + ELK).Reference(s)
[1] #112 (comment)
The text was updated successfully, but these errors were encountered: