35. Endpoints

Actuator endpoints allow you to monitor and interact with your application. Spring Boot includes a number of built-in endpoints and you can also add your own. For example the health endpoint provides basic application health information.

The way that endpoints are exposed will depend on the type of technology that you choose. Most applications choose HTTP monitoring, where the ID of the endpoint is mapped to a URL. For example, by default, the health endpoint will be mapped to /health.

The following endpoints are available:



Displays an auto-configuration report showing all auto-configuration candidates and the reason why they “were” or “were not” applied.



Displays a complete list of all the Spring Beans in your application.



Displays a collated list of all @ConfigurationProperties.



Performs a thread dump.



Exposes properties from Spring’s ConfigurableEnvironment.



Shows application health information (defaulting to a simple “OK” message).



Displays arbitrary application info.



Shows “metrics” information for the current application.



Displays a collated list of all @RequestMapping paths.



Allows the application to be gracefully shutdown (not enabled by default).



Displays trace information (by default the last few HTTP requests).



Depending on how an endpoint is exposed, the sensitive parameter may be used as a security hint. For example, sensitive endpoints will require a username/password when they are accessed over HTTP (or simply disabled if web security is not enabled).

35.1 Customizing endpoints

Endpoints can be customized using Spring properties. You can change if an endpoint is enabled, if it is considered sensitive and even its id.

For example, here is an application.properties that changes the sensitivity and id of the beans endpoint and also enables shutdown.


The prefix "endpoints + . + name" is used to uniquely identify the endpoint that is being configured.

35.2 Custom health information

The default information exposed by the health endpoint is a simple “OK” message. It is often useful to perform some additional health checks, for example you might check that a database connection works, or that a remote REST endpoint is functioning.

To provide custom health information you can register a Spring bean that implements the HealthIndicator interface.

import org.springframework.boot.actuate.health.HealthIndicator;
import org.springframework.stereotype.Component;

public class MyHealth implements HealthIndicator {

    public Health health() {
        // perform some specific health check
        return ...


Spring Boot provides a DataSourceHealthIndicator implementation that attempts a simple database test as well as implementations for Redis, MongoDB and RabbitMQ.

Spring Boot adds the HealthIndicator instances automatically if beans of type DataSource, MongoTemplate, RedisConnectionFactory, RabbitTemplate are present in the ApplicationContext.

Besides implementing custom a HealthIndicator type and using out-of-box Status types, it is also possible to introduce custom Status types for different or more complex system states. In that case a custom implementation of the HealthAggregator interface needs to be provided or the default implementation has to be configured using the health.status.order configuration property.

Assuming a new Status with code FATAL is being used in one of your HealthIndicator implementations. To configure the severity or order add the following to your application properties: health.status.order: FATAL, DOWN, UNKNOWN, UP.

35.3 Custom application info information

You can customize the data exposed by the info endpoint by setting info.* Spring properties. All Environment properties under the info key will be automatically exposed. For example, you could add the following to your application.properties:

info.app.description=My awesome service

If you are using Maven, you can automatically expand info properties from the Maven project using resource filtering. In your pom.xml you have (inside the <build/> element):


You can then refer to your Maven “project properties” via placeholders, e.g.

project.description=Demo project for info endpoint

In the above example we used project.* to set some values to be used as fallbacks if the Maven resource filtering has not been switched on for some reason.

35.3.1 Git commit information

Another useful feature of the info endpoint is its ability to publish information about the state of your git source code repository when the project was built. If a git.properties file is contained in your jar the git.branch and git.commit properties will be loaded.

For Maven users the spring-boot-starter-parent POM includes a pre-configured plugin to generate a git.properties file. Simply add the following declaration to your POM:


A similar gradle-git plugin is also available for Gradle users, although a little more work is required to generate the properties file.