Polish "Update endpoint enablement description to describe availability"

See gh-20799
This commit is contained in:
Andy Wilkinson 2020-04-09 12:38:05 +01:00
parent 399c85a5ef
commit 7e1807c01b
1 changed files with 4 additions and 4 deletions

View File

@ -48,10 +48,10 @@ Actuator endpoints let you monitor and interact with your application.
Spring Boot includes a number of built-in endpoints and lets you add your own. Spring Boot includes a number of built-in endpoints and lets you add your own.
For example, the `health` endpoint provides basic application health information. For example, the `health` endpoint provides basic application health information.
Each individual endpoint can be <<production-ready-endpoints-enabling-endpoints, enabled or disabled>>. Each individual endpoint can be <<production-ready-endpoints-enabling-endpoints, enabled or disabled>> and <<production-ready-endpoints-exposing-endpoints, exposed (made remotely accessible) over HTTP or JMX>>.
An endpoint that is enabled is said to be available if it is exposed (made remotely accessible) over HTTP or JMX. An endpoint is considered to be available when it is both enabled and exposed.
To be remotely accessible an endpoint also has to be <<production-ready-endpoints-exposing-endpoints, exposed via JMX or HTTP>>. The built-in endpoints will only be auto-configured when they are available.
Most applications choose HTTP, where the ID of the endpoint along with a prefix of `/actuator` is mapped to a URL. Most applications choose exposure via HTTP, where the ID of the endpoint along with a prefix of `/actuator` is mapped to a URL.
For example, by default, the `health` endpoint is mapped to `/actuator/health`. For example, by default, the `health` endpoint is mapped to `/actuator/health`.
The following technology-agnostic endpoints are available: The following technology-agnostic endpoints are available: