Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update documentation about endpoint enablement to reflect behaviour of @ConditionalOnAvailableEndpoint #20799

Closed
wants to merge 1 commit into from
Closed

Update documentation about endpoint enablement to reflect behaviour of @ConditionalOnAvailableEndpoint #20799

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc
View file
Open in desktop
Expand Up @@ -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 <<production-ready-endpoints-enabling-endpoints, enabled or disabled>>.
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 <<production-ready-endpoints-exposing-endpoints, exposed via JMX or HTTP>>.
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`.
Expand Down