Since there is no Heartbeat or InstanceRegisteredEvent when using the
SimpleDiscoveryClient we need to listen on the ApplicationReadyEvent
and register the configured instances

closes #505

With this commit two new properties were added to ease the client
configuration when used in servlet containers:
`spring.boot.admin.client.management-base-url` and
`spring.boot.admin.client.service-base-url`. Both properties can be used
to specify protocol, host and port for the urls. The paths will still be
guessed and appended to the base-urls. Additionally the servlet context
path is not read from the properties but from the ServletContext itself.

closes #488

Until now the thread querying the application endpoint can be blocked
for a very long time when the application is inresponsive. With this
commit two new properties `spring.boot.admin.monitor.read-timeout`
(default: 2s) and `spring.boot.admin.monitor.connect-timeout` (default:
5s) are added.

closes #462

A new property `spring.boot.admin.discovery.services` is added. It can
be used to restrict the services registered via discovery to a
whitelist (supporting simple patterns). Until now only blacklistin was
supported. The default whitelist permits all services.

Adds an new Notifier implementation for Let's Chat.

fixes #395

fixes #387

With this commit you can use simple patterns to match services to
ignore.
A pattern can look like this "foo*", "*foo", "foo*bar".

closes #377

With this commit you can specify either a URL or a serviceId for the
Turbine server location.
Note that `spring.boot.admin.turbin.url` is replaced by
`spring.boot.admin.turbine.location`.

closes #373

Added documentation and a sample on how to secure the SBA-Server and
leverage the new login ui-module

closes #361

This new ui-module provides a login page and a logout button.

closes #361

With this change it is possible to include credentials in the instance
metadata which will then be used to access the client endpoints using
HTTP Basic authorization.

closes #359

With this commit you can now associate your applications with custom
metadata using `spring.boot.admin.client.metadata.*` sensitive values
are recognized by key and are masked in the http interface.

This can be useful in the future if there are instance specific settings
which should be used by the admin server, e.g. custom notification
recipients.

For now there is no extra imetadata view in the ui. The values are shown
in the environment view.

With this commit the concept of an ApplicationFactory is introduced.
This allows you to easily modify the information used to register
your application at the admin server

closes #331

Add support for the /loggers endpoint from spring boot 1.5.x. With this
change log4j2 (and every other logging backend supported by spring boot)
is supported in the logging view.
The old implementation will be kept a while, so that the clients aren't
forced to migrate.

closes #305

With this commit the support for Turbine is completly revised. From now
on Turbine is supported via a separate module and is integrated as top
level view.

closes #306

As now with spring boot 1.4 there is a special goal for generating the build-
information, we use it for displaying the version in spring boot admin. The old
info.version property still works but is deprecated. From now on
build.info.version is taken into account.

With this commit you can specify the management.port for a discovered service
via the metadatamap.

With this commit you can from now on register the application on multiple
servers. You need to set spring.boot.admin.register-once to false and
assign a list of urls to spring.boot.admin.url

fixes #205

Use the metadata for health-/managament-url in the default service conversion.
This allows custom health- and management-path per application.

fixes #205

fixes #205

This adds a new FilteringNotifier which can use filters to suppres certain
events from being notified of. Two filter implementation are provided, one
filtering by name and one by id. Additional when a FilteringNotifier bean is
present, the autoconfiguration creates a REST-controller to add and remove
filters at runtime.