Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding a new console logger with INFO level #114

Open
jmaupetit opened this issue May 2, 2018 · 1 comment
Open

Consider adding a new console logger with INFO level #114

jmaupetit opened this issue May 2, 2018 · 1 comment

Comments

@jmaupetit
Copy link
Contributor

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 the INFO 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)

@sveetch
Copy link
Collaborator

sveetch commented Feb 28, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants