1. 16 Nov, 2017 1 commit
  2. 04 Nov, 2017 1 commit
  3. 24 Aug, 2017 1 commit
  4. 24 Jul, 2017 1 commit
  5. 23 Jul, 2017 1 commit
    • Improve the client configuration for usage in war-file deployments · 2848a637
      Johannes Edmeier authored
      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
  6. 30 May, 2017 1 commit
  7. 09 Feb, 2017 1 commit
  8. 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.
  9. 20 Nov, 2016 1 commit
    • Add ApplicationFactory · 3e16bad1
      rfelgentraeger authored
      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
  10. 16 Nov, 2016 1 commit
    • Respect management.ssl.* settings · 79eb9496
      Johannes Edmeier authored
      The managment.ssl.* properties needs to be taken into account when they
      are explicitly set and the managment.port differs from server.port
      
      fixes #333
  11. 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
  12. 17 Oct, 2016 1 commit
  13. 16 Oct, 2016 1 commit
  14. 11 Oct, 2016 2 commits
  15. 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
  16. 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
  17. 26 Aug, 2016 2 commits
    • 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
    • Use the SimpleClientHttpRequestFactory · c8be9561
      Johannes Edmeier authored
      Apparently when the Netty4ClientHttpRequestFactory is being used the content-
      lenght header is not being set in the POST request. Therefore the simple one is
      now being hardcoded to override decetion by the RestTemplateBuilder.
      
      fixes #248
  18. 10 Aug, 2016 2 commits
    • Fix all RestTemplateBuilders · 99369f27
      Johannes Edmeier authored
      Fix the usage of RestTemplateBuilders which wasn't covered by PR #247
    • Fix error in creating RestTemplate · 46bd004e
      reckter authored
      The RestTamplateBuilder doesn't save the arguments, it returns a new Builder instance, with the saved arguments. So you have to save the builder everytime you call a function on it.
  19. 15 Jul, 2016 2 commits
  20. 10 Jul, 2016 1 commit
  21. 27 Apr, 2016 2 commits
  22. 02 Mar, 2016 1 commit
    • Add spring.boot.admin.auto-registration property · 84cfa693
      Johannes Edmeier authored
      This commit contains multiple changes:
       - Start the registration task after the ApplicationReady event. This makes
         AdminClientProperties.isReady() unnecessary.
       - The RegistarApplicationListener has two new public methods to start/stop the
         periodic registration task.
       - Add spring.boot.admin.auto-registration property (default: true). When this
         property is set the registration task is automatically scheduled after the
         ApplicationReadyEvent.
      
      closes #151
  23. 25 Feb, 2016 1 commit
  24. 16 Feb, 2016 1 commit
    • Add spring.boot.admin.client.enabled property · 45a19cd4
      Robert Winkler authored
      Add spring.boot.admin.client.enabled property to explicitly disable the
      spring-boot-admin-client, (e.g. for unit tests). Defaults to true. The client is
      active when spring.boot.admin.client.enabled is true and spring.boot.admin.url
      is set.
      
      fixes #156
  25. 10 Jan, 2016 1 commit
    • Add option for fallback servers to register at · 25b3e509
      Johannes Edmeier authored
      In case you have clustered admin servers, you can now specify multiple urls for
      the client to register at. So that in the case the first server is down it will
      register at the next one specified in the list. This allows you to do cluster-
      ing without the need for a load-balanced host.
  26. 14 Dec, 2015 1 commit
  27. 13 Dec, 2015 1 commit
  28. 09 Dec, 2015 1 commit
    • Consider servlet-path for guessing management-url · a0ffe33a
      Johannes Edmeier authored
      Take the servlet-path into account when computing the management-/healht-url.
      This is not done for the service-url, since the main use-case for setting the
      servlet-path is to get the dispatcher-servlet out of the way for other servlets.
      
      fixes #133
  29. 21 Oct, 2015 3 commits
  30. 20 Oct, 2015 1 commit
  31. 30 Sep, 2015 1 commit
    • Add spring.boot.admin.client.preferIp · 7fe777db
      Johannes Stelzer authored
      In conjuntion with server.address / management.address this plays more nicely with interfaces with multiple ipAdrresses. Also remove spring.boot.admin.client.useAddressOf.
      
      fixes #112
  32. 24 Aug, 2015 2 commits