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

Move health.* properties to management.health.*

Browse Source 
Fixes gh-1841
This commit is contained in:
Stephane Nicoll
2014-11-07 07:19:22 +00:00
parent 27cbf45dbe
commit 00961611b2
7 changed files with 72 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
spring-boot-docs/src/main/asciidoc/appendix-application-properties.adoc
View File

@@ -398,8 +398,15 @@ content into your application; rather pick only the properties that you need.
endpoints.trace.enabled=true
# HEALTH INDICATORS
health.diskspace.path=.
health.diskspace.threshold=10485760
management.health.db.enabled=true
management.health.diskspace.enabled=true
management.health.mongo.enabled=true
management.health.rabbit.enabled=true
management.health.redis.enabled=true
management.health.solr.enabled=true
management.health.diskspace.path=.
management.health.diskspace.threshold=10485760
management.health.status.order: DOWN, OUT_OF_SERVICE, UNKNOWN, UP
# MVC ONLY ENDPOINTS
endpoints.jolokia.path=jolokia

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

@@ -174,11 +174,11 @@ Besides implementing custom a `HealthIndicator` type and using out-of-box {sc-sp
types, it is also possible to introduce custom `Status` types for different or more complex system
states. In that case a custom implementation of the {sc-spring-boot-actuator}/health/HealthAggregator.{sc-ext}[`HealthAggregator`]
interface needs to be provided or the default implementation has to be configured using the
`health.status.order` configuration property.
`management.health.status.order` configuration property.
Assuming a new `Status` with code `FATAL` is being used in one of your `HealthIndicator`
implementations. To configure the severity or order add the following to your application properties:
`health.status.order: FATAL, DOWN, UNKNOWN, UP`.
`management.health.status.order: DOWN, OUT_OF_SERVICE, UNKNOWN, UP`.