Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify loss of defaults when adding custom mapping

Browse Source 
See gh-20716
This commit is contained in:
Norio
2020-03-29 18:07:38 +09:00
committed by Andy Wilkinson
parent 4a0e8217f0
commit 9f009e4445
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
View File

@@ -760,6 +760,9 @@ For example, the following property maps `FATAL` to 503 (service unavailable):
management.endpoint.health.status.http-mapping.fatal=503
----
WARNING: A custom status mapping replaces whole of the default status mappings.
That means the above example has only one mapping to `FATAL` and any other statuses will return the http status 200 as `UNKNOWN` health status.
TIP: If you need more control, you can define your own `HttpCodeStatusMapper` bean.
The following table shows the default status mappings for the built-in statuses: