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.

Sign up for GitHub

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

Jump to bottom

Ability to specify the loglevel for console plugin #391

Closed
tino opened this issue Oct 20, 2015 · 2 comments
Closed

Ability to specify the loglevel for console plugin #391

tino opened this issue Oct 20, 2015 · 2 comments
Milestone
2.0

Comments

@tino
Copy link

tino commented Oct 20, 2015

Having all 'debug' and even 'info' message go to Sentry is not that usefull for me, while I still would like to see them on staging environments. It would be nice if the plugin could only sent them from a certain level up.
@mattrobenolt mattrobenolt added this to the 2.0 milestone Oct 22, 2015
@mattrobenolt
Copy link
Contributor

We need to figure out how to provide configuration for plugins overall. Schedulign this for 2.0.

@mattrobenolt mattrobenolt mentioned this issue Oct 22, 2015
Closed
@QuentinFchx
Copy link

It would also be nice if the console plugin would not override the logger property. Or default to console only if no logger property is set.

nevir added a commit to nevir/raven-js that referenced this issue Feb 24, 2016
@nevir
Configuration for the console plugin to choose levels. Fixes getsentr…
fe843e9 
…y#391.
benvinegar added a commit that referenced this issue Feb 29, 2016
@benvinegar
Merge pull request #514 from nevir/console-levels
40762d9 
Configuration for the console plugin to choose levels. Fixes #391.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
3 participants
@tino @mattrobenolt @QuentinFchx