Polish Elasticsearch health indicator
- Nest the configuration class in HealthIndicatorAutoConfiguration, bringing it into line with the other health indicator configuration classes - Include the statistics from the response in the health’s details - Map YELLOW to UP rather than UNKNOWN as it indicates that the cluster is running but that “the primary shard is allocated but replicas are not” [1]. The details can be used to determine the precise state of the cluster. - Add a property to configure the time that the health indicator will wait to receive a response from the cluster - Document the configuration properties - Update the tests to cover the updated functionality See gh-2399 [1] http://www.elastic.co/guide/en/elasticsearch/reference/1.x/cluster-health.html
This commit is contained in:
@@ -542,13 +542,15 @@ content into your application; rather pick only the properties that you need.
|
||||
|
||||
# HEALTH INDICATORS (previously health.*)
|
||||
management.health.db.enabled=true
|
||||
management.health.elasticsearch.enabled=true
|
||||
management.health.elasticsearch.response-timeout=100 # the time, in milliseconds, to wait for a response from the cluster
|
||||
management.health.diskspace.enabled=true
|
||||
management.health.diskspace.path=.
|
||||
management.health.diskspace.threshold=10485760
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user