Adding status indication to entities on middleware topology

[abonas]

This is a placeholder to discuss what is the relevant field/work needed for each entity to have the status color indication to be displayed for each entity on the middleware topology.

@miq-bot add_label enhancement, providers/hawkular

Currently this is needed for:

• provider - (the relevant check/method is the authentication status)
• middleware_server
• middleware_deployment
• middleware_datasource
• middleware_destination (jms topic/queue)

cc @pilhuhn please add your thoughts here

[pilhuhn]

See also https://issues.jboss.org/browse/HWKMETRICS-403

[abonas]

@pilhuhn why can't the server state field that is already fetched be used for the color status indication of a server? (this issue brought me to think about it)

[pilhuhn]

It can be used and #9147 is certainly a start. The issue is that it is only polled 'every now and then'.
We can more rely on it once we do targeted refresh on a single server when we get e.g. a "Server is down/going down" event from the Hawkular server.

And the server state is only enough for servers, but not for deployments where on would need to query availability.

[pilhuhn]

Opposite to what I wrote before about #9147 that server state is almost worthless in the sense that it is the internal view of the app server, which the agent reports from time to time. When the agent (which is inside the server) is down, it can't report the change to this internal state variable. it may be able to differentiate between running/admin mode, but not 'down'

[abonas]

@miq-bot move_issue manageiq-providers-hawkular

[miq-bot]

This issue has been moved to ManageIQ/manageiq-providers-hawkular#5