anchor.diff:  | Property name |Description |Default value
   
   | spring.boot.admin.context-path
  -| The context-path prefixes the path where the Admin Servers statics assets and API should be served. Relative to the Dispatcher-Servlet.
  +| The context-path prefixes the path where the Admin Server's statics assets and API should be served. Relative to the Dispatcher-Servlet.
   |
   
   | spring.boot.admin.monitor.period
  
positive.code: [[show-version-in-application-list]]
  === Show version in application list ===
  
  To get the version show up in the admins application list you have to set `info.version`. For example using maven filtering during the build:
  
  [source]
  .application.properties
  
negative.code: |
  
  | spring.boot.admin.discovery.converter.management-context-path
  | Will be appended to the service-url of the discovered service when the managment-url is converted by the `DefaultServiceInstanceConverter`.
  |
  
  | spring.boot.admin.discovery.converter.health-endpoint
  | Will be appended to the management-url of the discovered service when the health-url is converted by the `DefaultServiceInstanceConverter`.
  | `"health"`
  |===
  
  [[hazelcast-support]]
  === Hazelcast support ===
  Spring Boot Admin Server supports cluster replication with Hazelcast. It is automatically enabled when a `HazelcastConfig`- or `HazelcastInstance`-Bean is present. You can also configure the Hazelcast instance to be persistent, to keep the status over restarts.
  Also have a look at the http://docs.spring.io/spring-boot/docs/current-SNAPSHOT/reference/htmlsingle/#boot-features-hazelcast/[Spring Boot support for Hazelcast].
  
  . Add Hazelcast to your dependencies:
  