Skip to content

Conversation

GreyTeardrop
Copy link
Contributor

What was changed:

MicrometerClientStatsReporter no longer sets namingConvention on the MeterRegistry passed to it.

Why?

The MeterRegistry passed to the MicrometerClientStatsReporter might have some naming convention already set, and the creation of MicrometerClientStatsReporter would override it.

Also, the snakeCase convention is the default one for any MeterRegistry, 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

  1. Closes issue: fixes MicrometerClientStatsReporter overrides registry's naming convention #432
  2. How was this tested: unit test; ran client application with the altered version of MicrometerClientStatsReporter.

The MeterRegistry passed to the MicrometerClientStatsReporter might have
some naming convention already set, and creation of
MicrometerClientStatsReporter would override it.
@mfateev mfateev merged commit 6fa0fc9 into temporalio:master Apr 10, 2021
@GreyTeardrop GreyTeardrop deleted the dont-override-naming-convention branch April 10, 2021 20:50
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.

MicrometerClientStatsReporter overrides registry's naming convention

2 participants