anchor.diff:  Either you can include the `spring-boot-admin` client or use http://projects.spring.io/spring-cloud/spring-cloud.html[Spring Cloud Discovery] (e.g. Eureka)
   
   [[register-clients-via-spring-boot-admin]]
  -==== Register clients via spring-boot-admin-client ====
  +==== spring-boot-admin-starter-client ====
   
   Each application that want to register itself to the admin has to include the Spring Boot Admin Client.
   
  
positive.code: |
  |===
  
  [[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:
  
negative.code: 
  === Notifications ===
  
  [reminder-notifications]
  ==== Reminder notifications ====
  The `RemindingNotifier` sends reminders for down/offline applications, it delegates the sending of notifications to another notifier.
  
  By default a reminder is triggered when a registered application changes to `DOWN` or `OFFLINE`. You can alter this behaviour via `setReminderStatuses()`. The reminder ends when either the status changes to a non-triggering status or the regarding application gets deregistered.
  
  By default the reminders are sent every 10 minutes, to change this use `setReminderPeriod()`. The `RemindingNotifier` itself doesn't start the background thread to send the reminders, you need to take care of this as shown in the given example below;
  
  .How to configure reminders
  [source,java]
  ----
  @Configuration
  @EnableScheduling
  public class NotifierConfiguration {
      @Autowired
      private Notifier notifier;
  
  