Bug 1028084 - RFE: Extended availability metric
RFE: Extended availability metric
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
4.9
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-07 11:03 EST by Libor Zoubek
Modified: 2015-11-01 19:45 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Libor Zoubek 2013-11-07 11:03:26 EST
Description of problem:

Currently, availability metric has for different resources different meaning.

It is:

started/stopped for AS7 Managed Server resource
started/stopped or no long existing for AS Server resource
present/missing for most AS7 subsystems, deployments, datasources

To describe resource state, it's not enough. For example datasource can be enabled/disabled (I don't mean at JON level). It depends on plugin developer, how he understands resource state. He can export this "enabled/disabled" either using Trait metric or as a configuration property.

In any case, for user it is hard to know the real meaning of availability. for example:

JON is reporting AS7 managed server as DOWN, this means:
AS7 managed server is stopped
or AS7 managed server was removed from HC outside JON

User has to find out probably by trying to start it, which would result in error if server was removed.

As a solution we should somehow extend availability metric to be able to describe such situations. Or maybe, just let plugin somehow bind trait with availability. For example:

plugin API would define types for extended availability, say : ENABLED, DISABLED

in plugin-xml, developer would set trait metric with some "availability" attribute which would bind collecting this metric with availability scan. Then in plugin XML, developer would have to map possible trait values to ENABLED or DISABLED.

Then in UI we could instantly show different availability icon based on actual availability and this extended one.


Version-Release number of selected component (if applicable):
RHQ 4.9

Note You need to log in before you can comment on or make changes to this bug.