- `spring-boot-servlet` - `org.springframework.boot.servlet.autoconfigure.actuate.ServletHttpExchangesAutoConfiguration` - `org.springframework.boot.servlet.autoconfigure.actuate.ServletMappingsAutoConfiguration` - `spring-boot-webflux` - `org.springframework.boot.webflux.autoconfigure.actuate.web.WebFluxHttpExchangesAutoConfiguration ` - `org.springframework.boot.webflux.autoconfigure.actuate.web.WebFluxMappingsAutoConfiguration` - `spring-boot-webmvc` - `org.springframework.boot.webmvc.autoconfigure.actuate.web.WebMvcMappingsAutoConfiguration` `spring-boot-servlet` is the odd one out as the classes are in `actuate` rather than `actuate.web`. However, using that package leaves `spring-boot-servlet`'s `actuate.web` package to contain classes related to Actuator web endpoint infrastructure. In both `spring-boot-webflux` and `spring-boot-webmvc`, the `actuate.web` packages contain a mixture of lower-level infrastructure classes and higher-level contributions to the mappings and exchanges endpoints. I'm not 100% sure about the names, but I think the separation that we have in `spring-boot-servlet` is better.