-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Rebind log4j2 metrics if configuration is changed #5810
Open
pativa
wants to merge
4
commits into
micrometer-metrics:main
Choose a base branch
from
pativa:log4j2-reconfigure-rebind
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't want to block progress on this pull request, but in reviewing it, I've noticed something I think should be fixed perhaps first. We used to just have a single
MetricsFilter
instance. That was changed in #2183 whenMetricsFilter
was changed to take aLoggerConfig
. That was subsequently changed in 66f59e1 when the reason it was needed was fixed in log4j itself. I think we should have at that time changed back to using a single instance ofMetricsFilter
since its input is always the same for a given instance ofLog4j2Metrics
- theMeterRegistry
and tags. We're needlessly making multiple instances of equivalentMetricsFilter
s. Let me know if I'm missing something. I'll prepare a change for maintenance branches to stop making extraneous instances ofMetricsFilter
. If we get that merged, you can rebase your pull request on top of it and it will hopefully simplify things a bit./cc @jonatan-ivanov
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The case where it wouldn't always be the same
MeterRegistry
is if the same instance ofLog4j2Metrics
is bound to different registries. This came up before recently on whether that's expected/should be supported in all cases. I'm not sure we came to a conclusion as it depends on the implementation of theMeterBinder
. We'll have to discuss this.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was wondering about why multiple
MetricsFilter
were needed, but as it was that way I left that implementation. But it would be considerably easier to handle this without having multipleMetricsFilter
, yes (no reason to store it in a map and keeping track of which filter was used for which logger).If you change it to having a single filter, I can rebase this branch onto that and simplify this implementation a bit.
Having a single
MetricsFilter
wouldn't support binding the sameLog4j2Metrics
to different registries though, as you say.