1. 02 May, 2017 1 commit
  2. 15 Mar, 2017 1 commit
    • Add option to whitelist services from discovery · 11ca47c6
      Maxime RIVIERE authored
      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.
  3. 05 Mar, 2017 1 commit
  4. 26 Feb, 2017 1 commit
  5. 10 Feb, 2017 1 commit
  6. 15 Jan, 2017 1 commit
    • Remove CompositeRouteLocator · 17d7699d
      Johannes Edmeier authored
      My PR spring-cloud/spring-cloud-netflix#1448 has been merged into
      Dalston, therefore we can remove our implementation and need to fix some
      comile issues.
  7. 12 Jan, 2017 2 commits
  8. 08 Jan, 2017 2 commits
  9. 27 Dec, 2016 1 commit
  10. 26 Dec, 2016 2 commits
    • Polish · e91b8386
      Johannes Edmeier authored
    • 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
  11. 24 Dec, 2016 3 commits
  12. 17 Dec, 2016 1 commit
  13. 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.
  14. 10 Dec, 2016 1 commit
  15. 20 Nov, 2016 1 commit
    • Remember how the application was registered · 08b16417
      Johannes Edmeier authored
      From this commit on the source from wich the application was registered
      is remembered. We use this information for two things:
       * For applications which wasn't registered via the http-api the remove
         button is hidden.
       * The `ApplicationDiscoveryListener` only removes stale applications
         (those which are not anymore found via discovery) if the were registered
         via the `ApplicationDiscoeryListener`.
      
      closes #328
  16. 16 Nov, 2016 2 commits
  17. 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
  18. 02 Nov, 2016 1 commit
  19. 03 Oct, 2016 1 commit
  20. 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
  21. 16 Sep, 2016 1 commit
    • Make the AbstractNotifier work for any event. · af951b06
      Johannes Edmeier authored
      With this change the AbstractNotifier isn't specialized on status changes, but
      the default behaviour for the existing notifiers isn't changed.
      In addition the existing notifiers have been improved so that subclassing has
      become easier.
      To have existing notifiers acting on other events you need to override
      shouldNotify().
      
      fixes #270
  22. 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
  23. 28 Aug, 2016 1 commit
  24. 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
  25. 07 Aug, 2016 3 commits
  26. 10 Jul, 2016 1 commit
  27. 22 Jun, 2016 1 commit
    • Use Eureka's securedHealthUrl if available · f95f7a51
      Johannes Edmeier authored
      Sometimes Eureka only provides only the securedhealthUrl for the service.
      Previous to this commit the applciation won't be registered in that case. So
      with this commit the securedHealthUrl from Eureka is used, when available
      
      fixes #224
  28. 14 Jun, 2016 1 commit
  29. 11 Jun, 2016 1 commit
  30. 08 Jun, 2016 2 commits
  31. 02 Jun, 2016 1 commit