@ -8,7 +8,7 @@ The `auditevents` endpoint provides information about the application's audit ev
@@ -8,7 +8,7 @@ The `auditevents` endpoint provides information about the application's audit ev
[[audit-events-retrieving]]
== Retrieving Audit Events
To retrieve the audit events, make a `GET` request to `/application/auditevents`, as shown
To retrieve the audit events, make a `GET` request to `/actuator/auditevents`, as shown
@ -8,7 +8,7 @@ The `beans` endpoint provides information about the application's beans.
@@ -8,7 +8,7 @@ The `beans` endpoint provides information about the application's beans.
[[beans-retrieving]]
== Retrieving the Beans
To retrieve the beans, make a `GET` request to `/application/beans`, as shown in the
To retrieve the beans, make a `GET` request to `/actuator/beans`, as shown in the
@ -10,7 +10,7 @@ The `configprops` endpoint provides information about the application's
@@ -10,7 +10,7 @@ The `configprops` endpoint provides information about the application's
== Retrieving the `@ConfigurationProperties` Bean
To retrieve the `@ConfigurationProperties` beans, make a `GET` request to
`/application/configprops`, as shown in the following curl-based example:
`/actuator/configprops`, as shown in the following curl-based example:
@ -8,7 +8,7 @@ The `env` endpoint provides information about the application's `Environment`.
@@ -8,7 +8,7 @@ The `env` endpoint provides information about the application's `Environment`.
[[env-entire]]
== Retrieving the Entire Environment
To retrieve the entire environment, make a `GET` request to `/application/env`, as shown in
To retrieve the entire environment, make a `GET` request to `/actuator/env`, as shown in
@ -8,7 +8,7 @@ The `flyway` endpoint provides information about database migrations performed b
@@ -8,7 +8,7 @@ The `flyway` endpoint provides information about database migrations performed b
[[flyway-retrieving]]
== Retrieving the Migrations
To retrieve the migrations, make a `GET` request to `/application/flyway`, as shown in the
To retrieve the migrations, make a `GET` request to `/actuator/flyway`, as shown in the
@ -8,7 +8,7 @@ The `health` endpoint provides detailed information about the health of the appl
@@ -8,7 +8,7 @@ The `health` endpoint provides detailed information about the health of the appl
[[health-retrieving]]
== Retrieving the Health
To retrieve the health of the application, make a `GET` request to `/application/health`,
To retrieve the health of the application, make a `GET` request to `/actuator/health`,
@ -8,7 +8,7 @@ The `heapdump` endpoint provides a heap dump from the application's JVM.
@@ -8,7 +8,7 @@ The `heapdump` endpoint provides a heap dump from the application's JVM.
[[heapdump-retrieving]]
== Retrieving the Heap Dump
To retrieve the heap dump, make a `GET` request to `/application/heapdump`. The response
To retrieve the heap dump, make a `GET` request to `/actuator/heapdump`. The response
is binary data in https://docs.oracle.com/javase/8/docs/technotes/samples/hprof.html[
HPROF] format and can be large. Typically, you should save the response to disk for
subsequent analysis. When using curl, this can be achieved by using the `-O` option,
@ -9,7 +9,7 @@ The `info` endpoint provides general information about the application.
@@ -9,7 +9,7 @@ The `info` endpoint provides general information about the application.
== Retrieving the Info
To retrieve the information about the application, make a `GET` request to
`/application/info`, as shown in the following curl-based example:
`/actuator/info`, as shown in the following curl-based example:
@ -8,7 +8,7 @@ The `logfile` endpoint provides access to the contents of the application's log
@@ -8,7 +8,7 @@ The `logfile` endpoint provides access to the contents of the application's log
[[logfile-retrieving]]
== Retrieving the Log File
To retrieve the log file, make a `GET` request to `/application/logfile`, as shown in the
To retrieve the log file, make a `GET` request to `/actuator/logfile`, as shown in the
@ -8,7 +8,7 @@ The `shutdown` endpoint is used to shut down the application.
@@ -8,7 +8,7 @@ The `shutdown` endpoint is used to shut down the application.
[[shutdown-shutting-down]]
== Shutting Down the Application
To shut down the application, make a `POST` request to `/application/shutdown`, as shown
To shut down the application, make a `POST` request to `/actuator/shutdown`, as shown
@ -8,7 +8,7 @@ The `threaddump` endpoint provides a thread dump from the application's JVM.
@@ -8,7 +8,7 @@ The `threaddump` endpoint provides a thread dump from the application's JVM.
[[threaddump-retrieving]]
== Retrieving the Thread Dump
To retrieve the thread dump, make a `GET` request to `/application/threaddump`, as shown
To retrieve the thread dump, make a `GET` request to `/actuator/threaddump`, as shown
@ -25,8 +25,8 @@ Before you proceed, you should read the following topics:
@@ -25,8 +25,8 @@ Before you proceed, you should read the following topics:
[[overview-endpoint-urls]]
=== URLs
By default, all web endpoints are available beneath the path `/application` with URLs of
the form `/application/{id}`. The `/application` base path can be configured by using the
By default, all web endpoints are available beneath the path `/actuator` with URLs of
the form `/actuator/{id}`. The `/actuator` base path can be configured by using the
`management.endpoints.web.base-path` property, as shown in the following example:
[source,properties,indent=0]
@ -35,7 +35,7 @@ the form `/application/{id}`. The `/application` base path can be configured by
@@ -35,7 +35,7 @@ the form `/application/{id}`. The `/application` base path can be configured by
----
The preceding `application.properties` example changes the form of the endpoint URLs from
`/application/{id}` to `/manage/{id}`. For example, the URL `info` endpoint would become
`/actuator/{id}` to `/manage/{id}`. For example, the URL `info` endpoint would become
@ -69,7 +69,7 @@ public class BeansEndpointDocumentationTests extends AbstractEndpointDocumentati
@@ -69,7 +69,7 @@ public class BeansEndpointDocumentationTests extends AbstractEndpointDocumentati
@ -43,7 +43,7 @@ public class ConfigurationPropertiesReportEndpointDocumentationTests
@@ -43,7 +43,7 @@ public class ConfigurationPropertiesReportEndpointDocumentationTests
@ -50,7 +50,7 @@ public class FlywayEndpointDocumentationTests extends AbstractEndpointDocumentat
@@ -50,7 +50,7 @@ public class FlywayEndpointDocumentationTests extends AbstractEndpointDocumentat
@ -51,7 +51,7 @@ public class HealthEndpointDocumentationTests extends AbstractEndpointDocumentat
@@ -51,7 +51,7 @@ public class HealthEndpointDocumentationTests extends AbstractEndpointDocumentat
@ -48,7 +48,7 @@ public class InfoEndpointDocumentationTests extends AbstractEndpointDocumentatio
@@ -48,7 +48,7 @@ public class InfoEndpointDocumentationTests extends AbstractEndpointDocumentatio
@ -70,7 +70,7 @@ public class JolokiaManagementContextConfigurationIntegrationTests {
@@ -70,7 +70,7 @@ public class JolokiaManagementContextConfigurationIntegrationTests {
@ -79,7 +79,7 @@ public class JolokiaManagementContextConfigurationIntegrationTests {
@@ -79,7 +79,7 @@ public class JolokiaManagementContextConfigurationIntegrationTests {
@ -87,7 +87,7 @@ public class JolokiaManagementContextConfigurationIntegrationTests {
@@ -87,7 +87,7 @@ public class JolokiaManagementContextConfigurationIntegrationTests {
@ -95,7 +95,7 @@ public class JolokiaManagementContextConfigurationIntegrationTests {
@@ -95,7 +95,7 @@ public class JolokiaManagementContextConfigurationIntegrationTests {
@ -1125,7 +1125,7 @@ content into your application. Rather, pick only the properties that you need.
@@ -1125,7 +1125,7 @@ content into your application. Rather, pick only the properties that you need.
management.endpoints.web.enabled=true # Whether web endpoints are enabled
management.endpoints.web.expose=info,status # Endpoint IDs that should be exposed or '*' for all.
management.endpoints.web.exclude= # Endpoint IDs that should be excluded.
management.endpoints.web.base-path=/application # Base path for Web endpoints. Relative to server.context-path or management.server.context-path if management.server.port is configured.
management.endpoints.web.base-path=/actuator # Base path for Web endpoints. Relative to server.context-path or management.server.context-path if management.server.port is configured.
management.endpoints.web.path-mapping= # Mapping between endpoint IDs and the path that should expose them.
# ENDPOINTS CORS CONFIGURATION ({sc-spring-boot-actuator-autoconfigure}/endpoint/web/servlet/CorsEndpointProperties.{sc-ext}[CorsEndpointProperties])
@ -55,8 +55,8 @@ includes a number of built-in endpoints and lets you add your own. For example,
@@ -55,8 +55,8 @@ includes a number of built-in endpoints and lets you add your own. For example,
The way that endpoints are exposed depends on the type of technology that you choose.
Most applications choose HTTP monitoring, where the ID of the endpoint along with a
prefix of `/application` is mapped to a URL. For example, by default, the `health`
endpoint is mapped to `/application/health`.
prefix of `/actuator` is mapped to a URL. For example, by default, the `health`
endpoint is mapped to `/actuator/health`.
The following technology-agnostic endpoints are available:
@ -257,10 +257,10 @@ and `exclude` properties (see <<production-ready-endpoints-exposing-endpoints>>)
@@ -257,10 +257,10 @@ and `exclude` properties (see <<production-ready-endpoints-exposing-endpoints>>)
[[production-ready-endpoint-hypermedia]]
=== Hypermedia for Actuator Web Endpoints
A "`discovery page`" is added with links to all the endpoints. The "`discovery page`" is
available on `/application` by default.
available on `/actuator` by default.
When a custom management context path is configured, the "`discovery page`" automatically
moves from `/application` to the root of the management context. For example, if the
moves from `/actuator` to the root of the management context. For example, if the
management context path is `/management`, then the discovery page is available from
`/management`. When the management context path is set to `/`, the discovery page is
disabled to prevent the possibility of a clash with other mappings.
@ -269,13 +269,13 @@ disabled to prevent the possibility of a clash with other mappings.
@@ -269,13 +269,13 @@ disabled to prevent the possibility of a clash with other mappings.
[[production-ready-endpoint-custom-mapping]]
=== Actuator Web Endpoint Paths
By default, endpoints are exposed over HTTP under the `/application` path using ID of the
endpoint. For example, the `beans` endpoint is exposed under `/application/beans`. If you
By default, endpoints are exposed over HTTP under the `/actuator` path using ID of the
endpoint. For example, the `beans` endpoint is exposed under `/actuator/beans`. If you
want to map endpoints to a different path you can use the
`management.endpoints.web.path-mapping` property. You can also use
`management.endpoints.web.base-path` if you want change the base path.
Here's an example that remaps `/application/health` to `/healthcheck`:
Here's an example that remaps `/actuator/health` to `/healthcheck`:
@ -58,16 +58,16 @@ public class ManagementPortAndPathSampleActuatorApplicationTests {
@@ -58,16 +58,16 @@ public class ManagementPortAndPathSampleActuatorApplicationTests {
@ -76,7 +76,7 @@ public class ManagementPortAndPathSampleActuatorApplicationTests {
@@ -76,7 +76,7 @@ public class ManagementPortAndPathSampleActuatorApplicationTests {
@ -72,8 +72,8 @@ public class SampleActuatorCustomSecurityApplicationTests {
@@ -72,8 +72,8 @@ public class SampleActuatorCustomSecurityApplicationTests {
@ -81,7 +81,7 @@ public class SampleActuatorCustomSecurityApplicationTests {
@@ -81,7 +81,7 @@ public class SampleActuatorCustomSecurityApplicationTests {
@ -64,7 +64,7 @@ public class ManagementPortSampleActuatorApplicationTests {
@@ -64,7 +64,7 @@ public class ManagementPortSampleActuatorApplicationTests {
testHome();// makes sure some requests have been made
@ -73,7 +73,7 @@ public class ManagementPortSampleActuatorApplicationTests {
@@ -73,7 +73,7 @@ public class ManagementPortSampleActuatorApplicationTests {