1. 08 Jan, 2017 1 commit
  2. 27 Dec, 2016 1 commit
  3. 26 Dec, 2016 1 commit
    • Aggregate info on the server · 6fdaf8c1
      Johannes Edmeier authored
      The info is now fetched by the server on status change. This way the
      info can be used in the notifications and also improves performance when
      listing a huge amount of applications in the ui.
      
      closes #349
  4. 24 Dec, 2016 1 commit
  5. 17 Dec, 2016 1 commit
  6. 14 Dec, 2016 1 commit
    • Add metadata to the applications · 21c17900
      Johannes Edmeier authored
      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.
  7. 16 Nov, 2016 1 commit
    • Add details to the StatusInfo · 68173d87
      Johannes Edmeier authored
      The StatusInfo has a new details field. The StatusUpdater puts either the
      reponse from the health endpoint or the exception message in the details.
      This allows us to see the details over time (via the journal) and also to
      use `em in a bit more mail notifications.
      
      closes #329
  8. 15 Nov, 2016 1 commit
    • Detangle server from client · a99a889a
      Johannes Edmeier authored
      With this commits the server no longer depends on the client. The
      classes for the clients are moved to de.codecentric.boot.admin.client
      package.
      Since the perspective on applications is totally different from client
      and server the model has been split apart.
      
      What means this for users:
      1) The client is no longer a transitive dependency for your admin server
      you may need to add it explicitly to your dependencies, respectively
      jolokia-core in case you're using discovery and want to use the jmx-bean
      interface
      
      2)In case you have cutomised parts of the client you need to reflect the
      package change.
      
      fixes #332
  9. 26 Sep, 2016 1 commit
    • Don't ignore events from child contexts · 9304e6a4
      Johannes Edmeier authored
      With the fix for #260 we ignored all events from child contexts which turns out
      to be wrong since the "main" application context is, in case spring cloud config
      is used, is a child  of the bootstrap context. So we just act on the events from
      WebApplicationContexts. After they're fired up the needed port information is
      available.
      
      fixes #277
  10. 04 Sep, 2016 1 commit
    • Ignore events from child contexts · 0e9581fd
      Johannes Edmeier authored
      When includeing spring-cloud-netflix-hystrix-amqp to your application it looks
      like that the ApplicationReadyEvent is fired twice (from main and child
      application context). So we need to take care that only the events from the
      main applications are taken into account.
      
      fixes #260
  11. 26 Aug, 2016 1 commit
    • Prevent threads from surviving the application context shutdown. · d6478b2a
      Johannes Edmeier authored
      As it turns out (rather obvious) that the ThreadPools for registration and
      status updating needs to be destroyed on application shutdown so that the
      worker threads gets cancelled. To achieve this we simply register the
      ThreadPools as spring beans (since they are implementing DisposableBean).
      
      fixes #253
  12. 10 Jul, 2016 1 commit
  13. 22 May, 2016 1 commit
    • Add FilteringNotifier · 76c70039
      Johannes Edmeier authored
      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.
  14. 18 May, 2016 1 commit
  15. 09 Nov, 2015 1 commit
  16. 21 Oct, 2015 1 commit
    • Use Spring 4.2 events & consistent formatting · 3f4da621
      Johannes Edmeier authored
       * Use @EventListener instead of ApplicationListener-interface
       * Don't inherit ClientApplicationEvent from ApplicationEvent - so JournaledEvent isn't needed anymore
       * added eclipse formatter rules
       * reformatted all files
  17. 14 Sep, 2015 1 commit
  18. 30 May, 2015 1 commit
    • Added serverside health-checking. As prerequisite for mail-notification. · 0a931384
      Johannes Stelzer authored
      The health-check is made at a fixed interval (default: 10s) for all expired status-information (default-lifetime: 30s).
      The application health-endpoint must either respond with a JSON-Body having a status-field or with an empty body and all 2xx-http-responses are interpreted as UP and every other status as DOWN.
  19. 26 May, 2015 1 commit
  20. 26 Apr, 2015 1 commit
  21. 04 Mar, 2015 1 commit
  22. 17 Nov, 2014 1 commit
  23. 14 Nov, 2014 1 commit
    • Redesign Registry · ea931248
      Johannes Stelzer authored
      * Separate AppStore from AppRegistry
      * Allow Id generation to be altered
      * Remove logic from Application; Move id genretation into AppRegistry
      * Make AppStore threadSafe