Spring Boot 2 Actuator without Spring Boot and @EnableAutoConfiguration

Question

I am trying to set up Spring Actuator with existing Gradle Spring MVC project. I am not able to use @EnableAutoConfiguration. Unfortunately, I am not able to reach actuator endpoints, I think I am missing something.

The Spring dependencies in the project are:

// springVersion = 5.1.+
implementation(
            "org.springframework:spring-beans:$springVersion",
            "org.springframework:spring-webmvc:$springVersion",
            "org.springframework:spring-jdbc:$springVersion")

implementation 'org.springframework.boot:spring-boot-starter-actuator'

I am trying to configure project with following:

@Configuration
@Import({EndpointAutoConfiguration.class,
        MetricsEndpointAutoConfiguration.class,
        HealthEndpointAutoConfiguration.class,
        MappingsEndpointAutoConfiguration.class,
        InfoEndpointAutoConfiguration.class})
@EnableWebMvc
public class DI_App {

}

In properties file, I added:

management.endpoints.web.exposure.include=*

Non of actuator endpoints is enabled, I am getting 404 when trying to access them. I went through many related questions, but non of the solutions worked for me.

I might need to define custom EndpointHandlerMapping but not sure how to do this, it seems unavailable. (Ref: https://stackoverflow.com/a/53010693)

---

EDIT:
Currently, my app config looks like this:

@Configuration
@EnableWebMvc
@ComponentScan("com.test.springtest")
@Import({
        ConfigurationPropertiesReportEndpointAutoConfiguration.class,
        EndpointAutoConfiguration.class,
        WebEndpointAutoConfiguration.class,
        HealthEndpointAutoConfiguration.class,
        HealthIndicatorAutoConfiguration.class,
        InfoEndpointAutoConfiguration.class,
        InfoContributorAutoConfiguration.class,
        LogFileWebEndpointAutoConfiguration.class,
        LoggersEndpointAutoConfiguration.class,
        WebMvcMetricsAutoConfiguration.class,
        ManagementWebSecurityAutoConfiguration.class,
        ManagementContextAutoConfiguration.class,
        ServletManagementContextAutoConfiguration.class
})
public class DI_App {
    private final ApplicationContext _applicationContext;

    DI_App(ApplicationContext applicationContext) {
        _applicationContext = applicationContext;
        System.setProperty("management.endpoints.web.exposure.include", "*");
        System.setProperty("management.endpoints.jmx.exposure.exclude", "*");
        System.setProperty("management.endpoints.web.base-path", "/manage");
        System.setProperty("management.server.port", "10100");
    }

    @Bean
    public WebMvcEndpointHandlerMapping endpointHandlerMapping(Collection<ExposableWebEndpoint> endpoints) {
        List<String> mediaTypes = List.of(MediaType.APPLICATION_JSON_VALUE, ActuatorMediaType.V2_JSON);
        EndpointMediaTypes endpointMediaTypes = new EndpointMediaTypes(mediaTypes, mediaTypes);
        WebEndpointDiscoverer discoverer = new WebEndpointDiscoverer(_applicationContext,
                new ConversionServiceParameterValueMapper(),
                endpointMediaTypes,
                List.of(EndpointId::toString),
                emptyList(),
                emptyList());

        return new WebMvcEndpointHandlerMapping(new EndpointMapping("/manage"),
                endpoints,
                endpointMediaTypes,
                new CorsConfiguration(),
                new EndpointLinksResolver(discoverer.getEndpoints()));
    }
}

I had to add dispatcherServlet bean, in order to be able to add ManagementContextAutoConfiguration.class to Imports:

@Component
public class AppDispatcherServlet implements DispatcherServletPath {
    @Override
    public String getPath() {
        return "/";
    }
}

Current state is that when going to /manage endpoint I get this:

{"_links":{"self":{"href":"http://localhost:10100/dev/manage","templated":false},"info":{"href":"http://localhost:10100/dev/manage/info","templated":false}}}

But http://localhost:10100/dev/manage/info returns 404 and no other endpoints are available.

Answer 1

I'm using Maven, not Gradle, but was in a similar situation. I had a working spring-boot-actuator 1.4.2.RELEASE Health actuator endpoint with Spring MVC 4.3.21. Upgraded to spring-boot-starter-actuator 2.6.1 and Spring MVC 5.3.13 and the following works for me to reach /myAppContext/health.

The DispatcherServletAutoConfiguration import may be able to replace your explicit DispatcherServlet bean. My case doesn't include the Info actuator endpoint but the key thing for me was the specific Imports below. Order is somewhat important for certain imports, at least in my testing.

I know very little about spring boot so this is the result of enabling auto configuration, pouring through spring boot TRACE log output, and trying lots of different import combinations.

@Configuration
@EnableWebMvc
@Import({
        DispatcherServletAutoConfiguration.class,
        WebMvcAutoConfiguration.class,
        WebEndpointAutoConfiguration.class,
        EndpointAutoConfiguration.class,
        HealthEndpointAutoConfiguration.class,
        WebMvcEndpointManagementContextConfiguration.class
})

@PropertySource("classpath:/health.properties")
public class MyAppActuatorConfig {
    // 1.x version had EndpointHandlerMapping and HealthMvcEndpoint beans here.
    // There may be a more spring-boot-ish way to get this done : )
}

And a minimal health.properties that suited my deployment specifics where security was already in place:

management.endpoints.web.base-path=/

management.endpoint.health.show-details=when-authorized
management.endpoint.health.show-components=when-authorized