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

Resolve issue where more logs were forwarded than desired from MEL #1237

Merged
merged 11 commits into from
Sep 2, 2022

Conversation

JcolemanNR
Copy link
Contributor

@JcolemanNR JcolemanNR commented Sep 1, 2022

Description

Our instrumentation point for Microsoft Extensions Logging in agent log forwarding is invoked before any of the built in log level filtering has taken place. Due to this, logs with a lower level than what was configured in MEL were being forwarded to New Relic.

These changes resolve that issue by querying MEL to see if the level of observed log events are enabled or disabled.

Resolves #1230

Author Checklist

Reviewer Checklist

  • Perform code review
  • Pull request was adequately tested (new/existing tests, performance tests)
  • Review Changelog

Copy link
Member

@nr-ahemsath nr-ahemsath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good to me!

@JcolemanNR
Copy link
Contributor Author

Performance test results:

With Changes (additional log enabled check):
Logged 873129 messages in 2 minutes. 9-10% CPU
Logged 1015070 messages in 2 minutes. 8-10% CPU
Logged 995464 messages in 2 minutes. 8-11% CPU

Without changes:
Logged 872923 messages in 2 minutes. 8-11% CPU
Logged 1007570 messages in 2 minutes. 8-10% CPU

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

Successfully merging this pull request may close these issues.

Log forwarding does not respect configured level for Microsoft Extensions Logging
4 participants