Application name versus info.id about spring-boot-admin HOT 5 CLOSED

This is changed in my fork. There you will need spring.application.name and your actuator endpoint URL to register your app. Optionally you can provide info.version, info.hostname and info.ipaddress of your app.
And you can register multiple instances of your app. You will get a unique ID for each instance. The ID is stored as info.instanceId then.

from spring-boot-admin.

I'll commit my changes on wednesday

from spring-boot-admin.

This sounds neat, @RobWin. I'd love to take a look at the changes. Let me know when you have pushed them to your repo. In a (perhaps temporary/interim?) solution I just submitted as a pull request, I have gone with the spring.application.name as the key for registration of a specific instance. The info.id is something I intend to be the same for different instances of the same application. However, I am not entirely satisfied with my solution, so perhaps yours would be better. I look forward to taking a look at it.

from spring-boot-admin.

spring.application.name is correct. info.id has a more informational character. Maybe we can remove it. I will also think about it and discuss it with the team...

from spring-boot-admin.

I've commited my changes to my fork into the branch "telekom". You can have a look at it. I made a lot of changes within the admin-server project. I also added ExceptionHandling and Integration-Tests.
I still have to make changes in the admin-client project. I will change the registration/unregistration implementation and use the SmartLifecycle Interface of Spring to hook the registration/unregistration into the ApplicationContext Lifecycle.

from spring-boot-admin.