Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Sign in / Register
Toggle navigation
S
spring-boot
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
DEMO
spring-boot
Commits
399c85a5
Commit
399c85a5
authored
Apr 02, 2020
by
Eric Opoku
Committed by
Andy Wilkinson
Apr 09, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update endpoint enablement description to describe availability
See gh-20799
parent
e6c0a0dc
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
production-ready-features.adoc
...oot-docs/src/main/asciidoc/production-ready-features.adoc
+1
-1
No files found.
spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
View file @
399c85a5
...
@@ -49,7 +49,7 @@ Spring Boot includes a number of built-in endpoints and lets you add your own.
...
@@ -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.
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>>.
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>>.
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.
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`.
For example, by default, the `health` endpoint is mapped to `/actuator/health`.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment