Spring Boot中MeterBinders加载差异原因：为何部分未注入上下文

Great question! Let’s break down the exact reasons you’re seeing JvmGcMetrics in your Spring context but not JettyStatisticsMetrics:

1. Core JVM Metrics Are Enabled by Default #

JvmGcMetrics falls into Spring Boot’s "core monitoring" category. The JvmMetricsAutoConfiguration class registers it automatically as long as:

• You have spring-boot-starter-actuator and Micrometer dependencies on your classpath
• You haven’t explicitly disabled JVM metrics via properties like management.metrics.enable.jvm=false

Since tracking JVM health is a universal need for nearly all applications, these metrics are wired into the context by default with zero extra setup.

2. Jetty-Specific Metrics Require Strict Conditions #

JettyStatisticsMetrics is tied directly to the embedded Jetty web server, so Spring Boot only creates it as a bean when all these boxes are checked:

• You’re actually using embedded Jetty: The JettyMetricsAutoConfiguration uses @ConditionalOnClass({Server.class, StatisticsHandler.class}) to verify Jetty’s core server and statistics classes exist. If you’re running Tomcat or Undertow instead, this condition fails immediately.
• Jetty statistics are explicitly enabled: Even with Jetty on the classpath, you need to turn on statistics in your config. Add this property to your application.properties/application.yml:

  server.jetty.statistics-enabled=true
  

  Without this, the StatisticsHandler (which JettyStatisticsMetrics relies on to collect data) never initializes, so the binder won’t be registered.
• Actuator and Micrometer dependencies are present: Same as core metrics, you still need the base monitoring libraries to power the metrics pipeline.

3. How MeterRegistryPostProcessor Fits In #

You’re correct that MeterRegistryPostProcessor collects all MeterBinder beans from the context—but it can only work with beans that actually exist. If a binder’s auto-configuration conditions aren’t met, it never gets created as a bean in the first place, so the post-processor can’t find it.

Quick Checklist to Get JettyStatisticsMetrics Working #

If you want this binder to show up in your context:

• Swap out Tomcat/Undertow for spring-boot-starter-jetty as your web starter
• Add server.jetty.statistics-enabled=true to your config
• Double-check spring-boot-starter-actuator and your preferred Micrometer registry starter (like micrometer-registry-prometheus) are in your dependencies

内容的提问来源于stack exchange，提问作者user1293081