Do not override Micrometer's naming conventions #434
Merged
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.
What was changed:
MicrometerClientStatsReporter
no longer setsnamingConvention
on theMeterRegistry
passed to it.Why?
The
MeterRegistry
passed to theMicrometerClientStatsReporter
might have some naming convention already set, and the creation ofMicrometerClientStatsReporter
would override it.Also, the
snakeCase
convention is the default one for anyMeterRegistry
, so an explicit set would only be required if specific registry sets some other convention, in which case it might make sense to keep it as it.Checklist
MicrometerClientStatsReporter
.