From 399c85a5ef93f0be52eae60d2845d314299be8a7 Mon Sep 17 00:00:00 2001 From: Eric Opoku Date: Wed, 1 Apr 2020 20:02:42 -0400 Subject: [PATCH 1/2] Update endpoint enablement description to describe availability See gh-20799 --- .../src/main/asciidoc/production-ready-features.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc index d8c115a7dcc7..0355227a29ad 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc @@ -49,7 +49,7 @@ 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. Each individual endpoint can be <>. -This controls whether or not the endpoint is created and its bean exists in the application context. +An endpoint that is enabled is said to be available if it is exposed (made remotely accessible) over HTTP or JMX. To be remotely accessible an endpoint also has to be <>. Most applications choose 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`. From 7e1807c01b86ae720ba81cd1adb9080bd8e3d2e3 Mon Sep 17 00:00:00 2001 From: Andy Wilkinson Date: Thu, 9 Apr 2020 12:38:05 +0100 Subject: [PATCH 2/2] Polish "Update endpoint enablement description to describe availability" See gh-20799 --- .../src/main/asciidoc/production-ready-features.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc index 0355227a29ad..a8a14615dcfa 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc @@ -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. For example, the `health` endpoint provides basic application health information. -Each individual endpoint can be <>. -An endpoint that is enabled is said to be available if it is exposed (made remotely accessible) over HTTP or JMX. -To be remotely accessible an endpoint also has to be <>. -Most applications choose HTTP, where the ID of the endpoint along with a prefix of `/actuator` is mapped to a URL. +Each individual endpoint can be <> and <>. +An endpoint is considered to be available when it is both enabled and exposed. +The built-in endpoints will only be auto-configured when they are available. +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`. The following technology-agnostic endpoints are available: