properties not used spring.boot.admin.client.service-url
See original GitHub issuespring boot version : 1.5.1
spring boot admin : 1.5.2
I use SBA with eureka, not SBA client.
The SBA server set properties
management.context-path=/monitor
When I set properties
spring.boot.admin.client.service-url=http://hostname:8080/registry
, spring.boot.admin.client.management-url
spring.boot.admin.client.health-url,
at one service which registry to the eureka. The SBA server resolve the
serviceUrl=http://hostname:8080
.
So the SBA UI can’t get the service’s info or heath.
I have seen the Admin Starter Client ignoring Service, and try
spring.boot.admin.client.ignoreUnknownFields=true
,
It still wrong.
How can I set the properties?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7
Top Results From Across the Web
spring-boot-admin client custom health-url Invalid
I find the issue Admin Starter Client ignoring Service, However the properties is not useful spring.boot.admin.client.
Read more >Spring Boot Admin Reference Guide - GitHub Pages
The Spring Boot Admin Client registers the application at the admin server. This is done by periodically doing a HTTP post request to...
Read more >codecentric/spring-boot-admin - Gitter
The app running in a docker. with following app.properties: server.port = 9090 spring.boot.admin.client.management-url=http://host:9090
Read more >Spring Boot - Admin Client - Tutorialspoint
Now, add the Spring Boot Admin Server URL into your application properties file. For properties file users, add the following properties in the...
Read more >Spring Boot Admin | DevGlan
The server project is the web app itself that provides the admin console whereas client apps are all the microservices running for which...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
As I said you need to set
eureka.instance.metadata-map.management.context-path
andeureka.instance.metadata-map.management.context-port
Thanks for pointing out the metadata options. Small amendment, I believe eureka.instance.metadata-map.management.context-port should be eureka.instance.metadata-map.management.port. At least that’s what works for me.
As I said you need to set eureka.instance.metadata-map.management.context-path and eureka.instance.metadata-map.management.context-port