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

LoggingRule - Allow FinalMinLevel to override previous rules #4776

Merged
merged 1 commit into from
Jan 22, 2022

Conversation

snakefoot
Copy link
Contributor

@snakefoot snakefoot commented Jan 22, 2022

Followup to #4421, so one can do this:

<rules>
   <logger name="*" finalMinLevel="Info" />
   <logger name="Microsoft*" finalMinLevel="Warn" />
   <logger name="Microsoft.Hosting.Lifetime*" finalMinLevel="Info" /> <!-- Wins -->
   <logger name="System*" finalMinLevel="Warn" />

   <logger writeTo='defaultTarget' />
</rules>

Matching this:

{
  "Logging": {
    "LogLevel": { 
      "Default": "Info",
      "Microsoft": "Warning",
      "Microsoft.Hosting.Lifetime": "Info",
      "System": "Warning",
    }
}

@snakefoot snakefoot added the enhancement Improvement on existing feature label Jan 22, 2022
@snakefoot snakefoot added this to the 5.0 (new) milestone Jan 22, 2022
@sonarcloud
Copy link

sonarcloud bot commented Jan 22, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@snakefoot snakefoot merged commit 4b5ef2b into NLog:dev Jan 22, 2022
@snakefoot snakefoot deleted the finalminlevel-microsoft-style branch July 30, 2022 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement on existing feature size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant