anchor.diff:  [[production-ready-metrics-jdbc]]
   === DataSource metrics
   Auto-configuration will enable the instrumentation of all available `DataSources` with a
  -metric named `data.source`. Data source instrumentation results in gauges representing the
  -currently active, maximum allowed, and minimum allowed connections in the pool. Each of
  -these gauges has a name which is prefixed by `data.source` by default. The prefix can be
  -be customized using the `spring.metrics.jdbc.datasource-metric-name` property.
  +metric named `data.source`. Data source instrumentation results in gauges representing
  +the currently active, maximum allowed, and minimum allowed connections in the pool. Each
  +of these gauges has a name which is prefixed by `data.source` by default. The prefix can
  +be customized by using the `spring.metrics.jdbc.datasource-metric-name` property.
   
   Metrics will also be tagged by the name of the `DataSource` computed based on the bean
   name.
  
positive.code: 
  TIP: If you do this as a library feature, consider adding a configuration class annotated
  with `@ManagementContextConfiguration` to `/META-INF/spring.factories` under the key,
  `org.springframework.boot.actuate.autoconfigure.ManagementContextConfiguration`. If you do
  so and if your users ask for a separate management port or address, the endpoint moves to
  a child context with all the other web endpoints.
  
  
  
  [[production-ready-health]]
  === Health Information
  You can use health information to check the status of your running application. It is
  often used by monitoring software to alert someone when a production system goes down. The
  default information exposed by the `health` endpoint depends on how it is accessed. For an
  unauthenticated connection in a secure application, a simple '`status`' message is
  returned. For an authenticated connection, additional details are also displayed. (See
  <<production-ready-health-access-restrictions>> for HTTP details.)
  
  Health 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. By default, the final system state is
  derived by the `HealthAggregator`, which sorts the statuses from each `HealthIndicator`
  based on an ordered list of statuses. The first status in the sorted list is used as the
  overall health status. If no `HealthIndicator` returns a status that is known to the
  `HealthAggregator`, an `UNKNOWN` status is used.
  
  
  
  
negative.code: [[production-ready-application-info-env]]
  ==== Custom Application Information
  You can customize the data exposed by the `info` endpoint by setting `+info.*+` Spring
  properties. All `Environment` properties under the info key are automatically exposed.
  For example, you could add the following settings to your `application.properties` file:
  
  [source,properties,indent=0]
  ----
  