-
Notifications
You must be signed in to change notification settings - Fork 81
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
[HAL-1981] [Experimental] Console dashboard #579
base: main
Are you sure you want to change the base?
Conversation
This proposal is meant to discuss a dashboard for the next-gen console. In particular, I want to get feedback about:
|
|
||
*Sources* | ||
|
||
* `:read-resource(attributes-only,include-runtime)` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thinking out loud but should this card be dynamic to track changes in the running mode of the servers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to keep this static and move the running mode of the servers in the domain resp. runtime card.
|
||
== Requirements | ||
|
||
The dashboard visualizes WildFly's most essential data, including configuration and runtime data and links to valuable resources. Different cards visualize the data on the dashboard. If a card shows dynamic data, it includes a refresh button. In addition, all cards are refreshed automatically (for static cards this is a noop). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a card shows dynamic data
Do you infer that from the CLI operations or is it up to the card to define if it's dynamic or not?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's up to the card and part of the dashboard/card implementation. The cards are divided into static cards, like name, version, OS, and JVM information, which do not change at runtime, and dynamic cards, like deployment, memory, threads, and health information, which change at runtime.
* `/subsystem=microprofile-health-smallrye:check-ready` | ||
* `/subsystem=microprofile-health-smallrye:check-live` | ||
|
||
If the MicroProfile Health subsystem is not available, this card contains information on how to enable it and a link to https://docs.wildfly.org/32/Admin_Guide.html#MicroProfile_Health_SmallRye. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the MicroProfile Health subsystem is not present, you could also first check for the base health
subsystem too (eg if the server only uses the wildfly-ee galleon pack)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point!
https://issues.redhat.com/browse/HAL-1981