Mengaktifkan Endpoint Actuator

Spring Boot Actuator adds production-ready endpoints that expose the internal state of your running app: health, metrics, environment, beans, mappings, and more.

It turns a black-box service into something you can observe and operate without writing custom plumbing.

Enable Actuator by adding a single dependency. Auto-configuration registers the endpoints; no extra code is required.

By default endpoints live under /actuator. Visiting the base path returns a discovery document listing the exposed endpoints and their links.

Out of the box, only a few endpoints are exposed over HTTP — most notably health. Others exist but are hidden until you opt in, which is a safe default for production.

Control HTTP exposure with management.endpoints.web.exposure.include. List specific endpoints by id, or use * to expose all (use with care).

You can include broadly and then carve out sensitive endpoints with exclude, which takes precedence over include.

Exposure differs from being enabled. An endpoint can be enabled but not exposed. Toggle availability with management.endpoint.<id>.enabled.

The info endpoint surfaces arbitrary metadata about your build. Populate it from application.yml or build-time properties like git and build info.

You can relocate endpoints by changing management.endpoints.web.base-path, for example to /manage, to fit gateway or routing conventions.

For isolation, run Actuator on its own port with management.server.port. This lets you keep operational endpoints off the public application port entirely.

Actuator is the foundation of observability. Expose what operators need, hide what attackers could abuse, and treat the management surface as part of your security perimeter.

Actuator makes your app observable.

• Add spring-boot-starter-actuator
• Endpoints live under /actuator; only health is exposed by default
• Control HTTP exposure with exposure.include/exclude
• Enable/disable endpoints individually
• Optionally use a separate management port