-
Notifications
You must be signed in to change notification settings - Fork 865
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
Improve documentation on global logging level with multiple targets #1895
Comments
Line 1267 in 9259e13
|
I don't see how the linked option documentation would clear up the confusion. I think that it should be clearly stated here or here to make it clear that if you provide a list of |
Would you like to send a Pull Request to address this issue? |
Sure, will create one soon. |
The "global"
level
setting isn't taken into account whentransport.targets
parameter is provided - each target has its own level that defaults toinfo
(as mentioned here). That might be a bit confusing and should probably be mentioned in the documentation.For example originally having this config:
If I switch to the following, I'd lose
debug
logs:I appreciate that this might be an expected behaviour, but I'd expect this to be documented explicitly - I couldn't find the mention of it, unless I didn't look in the right place or I somehow missed it? It took me some time to figure out what's happening - it only started making sense when I've found the comment in the GitHub issue linked above.
The text was updated successfully, but these errors were encountered: