LoggerContext changes when using Spring Cloud

Hi,

I am using the Spring Boot 1.5 micrometer code and have found that the LoggerContext changes shortly after application startup (which I believe is related to our use of Spring Cloud). When the application starts io.micrometer.core.instrument.binder.logging.LogbackMetrics registers io.micrometer.core.instrument.binder.logging.MetricsTurboFilter, but when the application context is reloaded, LogbackMetrics is now pointing to the old LoggerContext. To get round this I created the following class:

@Component
public class FlexLogbackMetricsListener implements ApplicationListener<ContextRefreshedEvent> {

    private final LogbackMetrics logbackMetrics;
    private final MeterRegistry meterRegistry;

    public FlexLogbackMetricsListener(final LogbackMetrics logbackMetrics, final MeterRegistry meterRegistry) {
        this.logbackMetrics = logbackMetrics;
        this.meterRegistry = meterRegistry;
    }

    @Override
    public void onApplicationEvent(ContextRefreshedEvent event) {
       logbackMetrics.bindTo(meterRegistry);
    }

}

Is there a better way to do this? It works a treat, but does seem a little hacky.

Thanks

Nick

[nickcodefresh]

In the end this is what I managed to get working:

LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory();
boolean exists = loggerContext.getTurboFilterList().stream()
    .anyMatch(i -> i.getClass().getName().equals("io.micrometer.core.instrument.binder.logging.MetricsTurboFilter"));
if (!exists) {
    logbackMetrics.bindTo(meterRegistry);
}

[hnibbrig]

Hi. Unfortunately spring-cloud/spring-cloud-commons#608 didn’t fix this. The original workaround still works. @shakuzen will you reopen this?

This issue would be reopened if there were some change to make in Micrometer itself. So far all the discussed solutions have been changes in other projects. The resolution of the linked spring-cloud-commons issue indicates to me that it should not be a problem since the 2020.0.0-M4 release of Spring Cloud.

You are completely right. I will head over to the spring-cloud-commons project and refer to this bug. Maybe they can help out some more. Thanks for the quick reply!