| Key: |
RHQ-704
|
| Type: |
Bug
|
| Status: |
Accepted
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Ian Springer
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
RHQ Project
Created: 31/Jul/08 01:14 PM
Updated: 12/Dec/08 11:56 PM
|
|
| Component/s: |
Plugins
|
| Affects Version/s: |
1.1pre
|
| Fix Version/s: |
None
|
|
| Date of First Response: |
14/Sep/08 02:30 PM
|
| VCS Revision: |
1,149
|
|
The metric is currently defined in the descriptor as follows:
<metric property="Uptime"
displayName="Up Time"
description="Total number of seconds since the agent was started"
defaultOn="true"
units="seconds"
category="availability"
measurementType="dynamic" /> <!-- changed to dynamic to prevent generation of per Minute metric. -->
Unfortunately, by changing its type to "dynamic", it will be tracked for OOBs, which doesn't make sense for up time, since it monotonically increases.
We need a way to either:
1) disable per-minute metrics for a trendsup metric (one idea is to disable per-minute metrics for trendsup metrics that have units of "seconds")
2) disable baseline OOB tracking for dynamic metrics, e.g.:
<metric property="Uptime"
displayName="Up Time"
description="Total number of seconds since the agent was started"
defaultOn="true"
units="seconds"
category="availability"
disableBaselines="true"
measurementType="dynamic" /> <!-- changed to dynamic to prevent generation of per Minute metric. -->
|
|
Description
|
The metric is currently defined in the descriptor as follows:
<metric property="Uptime"
displayName="Up Time"
description="Total number of seconds since the agent was started"
defaultOn="true"
units="seconds"
category="availability"
measurementType="dynamic" /> <!-- changed to dynamic to prevent generation of per Minute metric. -->
Unfortunately, by changing its type to "dynamic", it will be tracked for OOBs, which doesn't make sense for up time, since it monotonically increases.
We need a way to either:
1) disable per-minute metrics for a trendsup metric (one idea is to disable per-minute metrics for trendsup metrics that have units of "seconds")
2) disable baseline OOB tracking for dynamic metrics, e.g.:
<metric property="Uptime"
displayName="Up Time"
description="Total number of seconds since the agent was started"
defaultOn="true"
units="seconds"
category="availability"
disableBaselines="true"
measurementType="dynamic" /> <!-- changed to dynamic to prevent generation of per Minute metric. -->
|
Show » |
|
UpTime metric on RHQ Agent resource type should not be tracked for baseline OOBs
But then there are metrics like "cpu time spent in user mode" where a per minute metric makes sense.
2) Adds a lot of stuff to the whole data model
An alternative could be to add a 'perMinute' attribute to the schema, that is true by default and which only gets parsed in org.rhq.core.clientapi.agent.metadata.MetricsMetadataParser.parseMetricsMetadata(MetricDescriptor, ResourceType) in the if-clause to determine if per minute data should be created. This new attribute would only apply to trendsup/down.
Or we could create trends{up,down}nopermin measurement types