Spring Boot monitor and manage application after push to
production by using HTTP endpoints or with JMX. Auditing, health,
and metrics gathering can also be automatically applied to your
The 'spring-boot-actuator' module provides all of Spring Boot's
production ready features.
Actuator endpoints let you monitor and interact with your
application. Each individual endpoint can be enabled or disabled
(specify in application property file or YAML). Once created and its
bean exists in the application context.
Some endpoints are auditevents, caches, health, loggers,
shutdown, threaddump etc.
If you add a @Bean annotated with @Endpoint, any methods
annotated with @ReadOperation, @WriteOperation, or @DeleteOperation
are automatically exposed over JMX and in a web application, over
HTTP as well.
Health endpoint depends on the
management.endpoint.health.show-components properties which can be
configured with one of these values - never, when-authorized, always
The HealthContributorRegistry can be used to register and
unregister health indicators at runtime.
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 BuildProperties bean is available, the info endpoint can
also publish information about your build.
Exposing management endpoints by using the default HTTP port is a
sensible choice for cloud-based deployments. Application runs inside
your own data center, you may prefer to expose endpoints by using a
different HTTP port.
When configured to use a custom port, the management server can
also be configured with its own SSL by using the various
If you do not want to expose endpoints over HTTP, you can set the
management port to -1 i.e. management.server.port=-1
Metrics facade that supports numerous monitoring systems