-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use bus-refresh endpoint if enabled / Allow refresh on multiple instances #1187
Comments
If the bus-refresh JMX Endpoint is enabled for your Admin Server, you should be able to achieve this using the JVM/JMX page, under the |
Imho there are two (additive?) solutions to this:
|
Yes ,we can trigger it manually using cURL , but we would like to trigger it on Spring Boot Admin Web UI, currently the button "Refresh Context" will only trigger actuator/refresh. If there is a new button that can trigger actuator/bus-refresh , will be more convenient to people especially when they don't know how to trigger at JVM page / Fire the request themselves. |
Before I discovered SBA I had to write a bespoke service to call the You already have all the instances so just need to call each endpoint for each pod |
Based on the current SBA front-end design, we can click on an instance and refresh the context of a particular property to our liking.
However, when there are too many instances (imagine there are 30 of them), we need to manually refresh the property in each instance and repeating it for 30 times can be cumbersome.
I would like to know if Spring Boot Admin supports the property propagation for all other instances of the same name if a property is refreshed on one instance, i.e. through "actuator/bus-refresh". Else, I would like this to be a feature request.
The text was updated successfully, but these errors were encountered: