Skip to content
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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

hpehl
Copy link
Contributor

@hpehl hpehl commented Jun 7, 2024

@hpehl
Copy link
Contributor Author

hpehl commented Jun 7, 2024

This proposal is meant to discuss a dashboard for the next-gen console. In particular, I want to get feedback about:

  • the cards on the dashboard
  • the information on the cards
  • distinction between standalone and domain mode
  • whether the cards should be refreshed automatically or only on demand

@hpehl hpehl changed the title HAL-1981: Console dashboard [HAL-1981][Experimental] Console dashboard Jun 7, 2024
@hpehl hpehl changed the title [HAL-1981][Experimental] Console dashboard [HAL-1981] [Experimental] Console dashboard Jun 7, 2024

*Sources*

* `:read-resource(attributes-only,include-runtime)`
Copy link
Member

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?

Copy link
Contributor Author

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).
Copy link
Member

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?

Copy link
Contributor Author

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.
Copy link
Member

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)

Copy link
Contributor Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants