NLog unexpectedly writing to log with lower level restriction - log level being ignored
I'm confused by NLog logging level fallbacks. I have this set of rules:
<rules>
<!-- Send Microsoft into a black hole to hide their logs -->
<logger name="Microsoft.*" maxLevel="Warn" final="true" />
<logger name="commands" minlevel="Info" writeTo="logger" final="true" />
<logger name="*" minlevel="Trace" writeTo="logger" />
<logger name="exception" minlevel="Error" writeTo="publisher" final="true" />
</rules>
What I expect to happen is that anything with a logger name of "commands" will only be logged at Info level or above. Any other logger name will be logged regardless.
What's happening is that when I get the logger for "commands" and I check its properties every log level is enabled, so if I provide a log level of Debug, then it's still logged. From what I understand, this shouldn't be the case.
I think this is something to do with my fallback logger (the name="*") I believe the "final=true" on the "commmand" logger should any further logging checks.
This is running in .net core
Am I misunderstanding how this works?
nlog
asked Nov 20 '18 at 12:19
GrahamB
456721
add a comment |
I'm confused by NLog logging level fallbacks. I have this set of rules:
<rules>
<!-- Send Microsoft into a black hole to hide their logs -->
<logger name="Microsoft.*" maxLevel="Warn" final="true" />
<logger name="commands" minlevel="Info" writeTo="logger" final="true" />
<logger name="*" minlevel="Trace" writeTo="logger" />
<logger name="exception" minlevel="Error" writeTo="publisher" final="true" />
</rules>
What I expect to happen is that anything with a logger name of "commands" will only be logged at Info level or above. Any other logger name will be logged regardless.
What's happening is that when I get the logger for "commands" and I check its properties every log level is enabled, so if I provide a log level of Debug, then it's still logged. From what I understand, this shouldn't be the case.
I think this is something to do with my fallback logger (the name="*") I believe the "final=true" on the "commmand" logger should any further logging checks.
This is running in .net core
Am I misunderstanding how this works?
nlog
asked Nov 20 '18 at 12:19
GrahamB
456721
You can read about logging-rules here: github.com/NLog/NLog/wiki/Configuration-file#rules . They are evaluated from top to bottom, and final will stop further evaluation. But when using minLevel="Info" with final="true" then it will only stop the logevents with that loglevel (or higher like Warn+Error). Will not stop LogEvents with LogLevel.Trace or Debug from flowing down to the next rules that has minLevel="Trace".
– Rolf Kristensen
Nov 20 '18 at 18:43
add a comment |
I'm confused by NLog logging level fallbacks. I have this set of rules:
<rules>
<!-- Send Microsoft into a black hole to hide their logs -->
<logger name="Microsoft.*" maxLevel="Warn" final="true" />
<logger name="commands" minlevel="Info" writeTo="logger" final="true" />
<logger name="*" minlevel="Trace" writeTo="logger" />
<logger name="exception" minlevel="Error" writeTo="publisher" final="true" />
</rules>
What I expect to happen is that anything with a logger name of "commands" will only be logged at Info level or above. Any other logger name will be logged regardless.
What's happening is that when I get the logger for "commands" and I check its properties every log level is enabled, so if I provide a log level of Debug, then it's still logged. From what I understand, this shouldn't be the case.
I think this is something to do with my fallback logger (the name="*") I believe the "final=true" on the "commmand" logger should any further logging checks.
This is running in .net core
Am I misunderstanding how this works?
nlog
asked Nov 20 '18 at 12:19
GrahamB
456721
I'm confused by NLog logging level fallbacks. I have this set of rules:
<rules>
<!-- Send Microsoft into a black hole to hide their logs -->
<logger name="Microsoft.*" maxLevel="Warn" final="true" />
<logger name="commands" minlevel="Info" writeTo="logger" final="true" />
<logger name="*" minlevel="Trace" writeTo="logger" />
<logger name="exception" minlevel="Error" writeTo="publisher" final="true" />
</rules>
What I expect to happen is that anything with a logger name of "commands" will only be logged at Info level or above. Any other logger name will be logged regardless.
What's happening is that when I get the logger for "commands" and I check its properties every log level is enabled, so if I provide a log level of Debug, then it's still logged. From what I understand, this shouldn't be the case.
I think this is something to do with my fallback logger (the name="*") I believe the "final=true" on the "commmand" logger should any further logging checks.
This is running in .net core
Am I misunderstanding how this works?
nlog
nlog
asked Nov 20 '18 at 12:19
GrahamB
456721
asked Nov 20 '18 at 12:19
GrahamB
456721
asked Nov 20 '18 at 12:19
GrahamB
456721
asked Nov 20 '18 at 12:19
GrahamB
456721
asked Nov 20 '18 at 12:19
GrahamB
456721
456721
You can read about logging-rules here: github.com/NLog/NLog/wiki/Configuration-file#rules . They are evaluated from top to bottom, and final will stop further evaluation. But when using minLevel="Info" with final="true" then it will only stop the logevents with that loglevel (or higher like Warn+Error). Will not stop LogEvents with LogLevel.Trace or Debug from flowing down to the next rules that has minLevel="Trace".
– Rolf Kristensen
Nov 20 '18 at 18:43
add a comment |
You can read about logging-rules here: github.com/NLog/NLog/wiki/Configuration-file#rules . They are evaluated from top to bottom, and final will stop further evaluation. But when using minLevel="Info" with final="true" then it will only stop the logevents with that loglevel (or higher like Warn+Error). Will not stop LogEvents with LogLevel.Trace or Debug from flowing down to the next rules that has minLevel="Trace".
– Rolf Kristensen
Nov 20 '18 at 18:43
You can read about logging-rules here: github.com/NLog/NLog/wiki/Configuration-file#rules . They are evaluated from top to bottom, and final will stop further evaluation. But when using minLevel="Info" with final="true" then it will only stop the logevents with that loglevel (or higher like Warn+Error). Will not stop LogEvents with LogLevel.Trace or Debug from flowing down to the next rules that has minLevel="Trace".
– Rolf Kristensen
Nov 20 '18 at 18:43
You can read about logging-rules here: github.com/NLog/NLog/wiki/Configuration-file#rules . They are evaluated from top to bottom, and final will stop further evaluation. But when using minLevel="Info" with final="true" then it will only stop the logevents with that loglevel (or higher like Warn+Error). Will not stop LogEvents with LogLevel.Trace or Debug from flowing down to the next rules that has minLevel="Trace".
– Rolf Kristensen
Nov 20 '18 at 18:43
add a comment |
1 Answer
1
active
oldest
votes
Maybe this will work:
<rules>
<!-- Send Microsoft into a black hole to hide their logs -->
<logger name="Microsoft.*" maxLevel="Warn" final="true" />
<logger name="commands" maxLevel="Debug" final="true" />
<logger name="commands" minlevel="Info" writeTo="logger" final="true" />
<logger name="*" minlevel="Trace" writeTo="logger" />
<logger name="exception" minlevel="Error" writeTo="publisher" final="true" />
</rules>
answered Nov 20 '18 at 18:45
Rolf Kristensen
5,1952435
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53392862%2fnlog-unexpectedly-writing-to-log-with-lower-level-restriction-log-level-being%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Maybe this will work:
<rules>
<!-- Send Microsoft into a black hole to hide their logs -->
<logger name="Microsoft.*" maxLevel="Warn" final="true" />
<logger name="commands" maxLevel="Debug" final="true" />
<logger name="commands" minlevel="Info" writeTo="logger" final="true" />
<logger name="*" minlevel="Trace" writeTo="logger" />
<logger name="exception" minlevel="Error" writeTo="publisher" final="true" />
</rules>
answered Nov 20 '18 at 18:45
Rolf Kristensen
5,1952435
add a comment |
Maybe this will work:
<rules>
<!-- Send Microsoft into a black hole to hide their logs -->
<logger name="Microsoft.*" maxLevel="Warn" final="true" />
<logger name="commands" maxLevel="Debug" final="true" />
<logger name="commands" minlevel="Info" writeTo="logger" final="true" />
<logger name="*" minlevel="Trace" writeTo="logger" />
<logger name="exception" minlevel="Error" writeTo="publisher" final="true" />
</rules>
answered Nov 20 '18 at 18:45
Rolf Kristensen
5,1952435
add a comment |
Maybe this will work:
<rules>
<!-- Send Microsoft into a black hole to hide their logs -->
<logger name="Microsoft.*" maxLevel="Warn" final="true" />
<logger name="commands" maxLevel="Debug" final="true" />
<logger name="commands" minlevel="Info" writeTo="logger" final="true" />
<logger name="*" minlevel="Trace" writeTo="logger" />
<logger name="exception" minlevel="Error" writeTo="publisher" final="true" />
</rules>
answered Nov 20 '18 at 18:45
Rolf Kristensen
5,1952435
Maybe this will work:
<rules>
<!-- Send Microsoft into a black hole to hide their logs -->
<logger name="Microsoft.*" maxLevel="Warn" final="true" />
<logger name="commands" maxLevel="Debug" final="true" />
<logger name="commands" minlevel="Info" writeTo="logger" final="true" />
<logger name="*" minlevel="Trace" writeTo="logger" />
<logger name="exception" minlevel="Error" writeTo="publisher" final="true" />
</rules>
answered Nov 20 '18 at 18:45
Rolf Kristensen
5,1952435
answered Nov 20 '18 at 18:45
Rolf Kristensen
5,1952435
answered Nov 20 '18 at 18:45
Rolf Kristensen
5,1952435
answered Nov 20 '18 at 18:45
Rolf Kristensen
5,1952435
5,1952435
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53392862%2fnlog-unexpectedly-writing-to-log-with-lower-level-restriction-log-level-being%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You can read about logging-rules here: github.com/NLog/NLog/wiki/Configuration-file#rules . They are evaluated from top to bottom, and final will stop further evaluation. But when using minLevel="Info" with final="true" then it will only stop the logevents with that loglevel (or higher like Warn+Error). Will not stop LogEvents with LogLevel.Trace or Debug from flowing down to the next rules that has minLevel="Trace".
– Rolf Kristensen
Nov 20 '18 at 18:43