anchor.diff:  
   
   [[production-ready-health]]
  -=== Custom health information
  -The default information exposed by the `health` endpoint is a simple '`OK`' message. It
  -is often useful to perform some additional health checks, for example you might check
  -that a database connection works, or that a remote REST endpoint is functioning.
  -
  -To provide custom health information you can register a Spring bean that implements the
  +=== Health information
  +Health information can be used to check the status of your running application. It is
  +often used by monitoring software to alert someone if a production system goes down.
  +The default information exposed by the `health` endpoint depends on how it is accessed.
  +For an insecure unauthenticated connection a simple '`status`' message is returned, for a
  +secure or authenticated connection additional details are also displayed (see
  +<<production-ready-health-access-restrictions>> for HTTP details).
  +
  +Heath information is collected from all
  +{sc-spring-boot-actuator}/health/HealthIndicator.{sc-ext}[`HealthIndicator`] beans defined
  +in your `ApplicationContext`. Spring Boot includes a number of auto-configured
  +`HealthIndicators` and you can also write your own.
  +
  +
  +
  +=== Security with HealthIndicators
  +Information returned by `HealthIndicators` is often somewhat sensitive in nature. For
  +example and you probably don't want to publish details of your database server to the
  +world. For this reason, by default, only the health status is exposed on an insecure HTTP
  +connection. If you are happy for complete heath information to always be exposed you can
  +set `endpoints.health.sensitive` to `false`.
  +
  +Heath responses are also cached to prevent "`denial of service`" attacks. Use the
  +`endpoints.health.time-to-live` property if you want to change the default cache period
  +of 1000 milliseconds.
  +
  +
  +
  +==== Auto-configured HealthIndicators
  +The following `HealthIndicators` are auto-configured by Spring Boot when appropriate:
  +
  +|===
  +|Name |Description
  +
  +|{sc-spring-boot-actuator}/health/DiskSpaceHealthIndicator.{sc-ext}[`DiskSpaceHealthIndicator`]
  +|Checks for low disk space.
  +
  +|{sc-spring-boot-actuator}/health/DataSourceHealthIndicator.{sc-ext}[`DataSourceHealthIndicator`]
  +|Checks that a connection to `DataSource` can be obtained.
  +
  +|{sc-spring-boot-actuator}/health/MongoHealthIndicator.{sc-ext}[`MongoHealthIndicator`]
  +|Checks that a Mongo database is up.
  +
  +|{sc-spring-boot-actuator}/health/RabbitHealthIndicator.{sc-ext}[`RabbitHealthIndicator`]
  +|Checks that a Rabbit server is up.
  +
  +|{sc-spring-boot-actuator}/health/SolrHealthIndicator.{sc-ext}[`RedisHealthIndicator`]
  +|Checks that a Redis server is up.
  +
  +|{sc-spring-boot-actuator}/health/SolrHealthIndicator.{sc-ext}[`SolrHealthIndicator`]
  +|Checks that a Solr server is up.
  +|===
  +
  +
  +
  +==== Writing custom HealthIndicators
  +To provide custom health information you can register Spring beans that implement the
   {sc-spring-boot-actuator}/health/HealthIndicator.{sc-ext}[`HealthIndicator`] interface.
  +You need to provide an implementation of the `health()` method and return a `Health`
  +response. The `Health` response should include a status and can optionally include
  +additional details to be displayed.
   
   [source,java,indent=0]
   ----
  
positive.code: |true
  
  |`health`
  |Shows application health information (defaulting to a simple '`OK`' message).
  |false
  
  |`info`
  |Displays arbitrary application info.
  
negative.code: 
  
  [[production-ready-health-access-restrictions]]
  === HTTP Health endpoint access restrictions
  The information exposed by the health endpoint varies depending on whether or not it's
  accessed anonymously. By default, when accessed anonymously, any details about the
  server's health are hidden and the endpoint will simply indicate whether or not the server
  