Clarify loss of defaults when adding custom mapping

See spring-projectsgh-20716
russellyou · Jun 8, 2020 · 9f009e4 · 9f009e4
1 parent 4a0e821
commit 9f009e4
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/...-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/...-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
@@ -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: