Description
Expected Behavior
Exposed metrics are filtered according to defined MeterRegistryCustomizer.
Actual Behavior
io.temporal.spring.boot.autoconfigure.NonRootNamespaceAutoConfiguration#nonRootBeanPostProcessor causes early initialization of MeterRegistry (through io.temporal.spring.boot.autoconfigure.MetricsScopeAutoConfiguration#scope), even before org.springframework.boot.actuate.autoconfigure.metrics.MeterRegistryPostProcessor is ready. This makes
any MeterRegistryCustomizer effectively ignored.
Steps to Reproduce the Problem
I prepared small reproducer project: https://github.com/rpost/temporal-bug:
- rpost/temporal-bug@d97d735 introduces setup and adds test which proves metrics being filtered accordingly.
- rpost/temporal-bug@0a77f4a adds temporal client and this makes test broken
- rpost/temporal-bug@d16476e contains workaround