Bug 994226

Summary: RFE: Add Current late collections metric
Product: [JBoss] JBoss Operations Network Reporter: Viet Nguyen <vnguyen>
Component: Monitoring -- OtherAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED WONTFIX QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: fbrychta, jshaughn, loleary
Target Milestone: ---Keywords: FutureFeature
Target Release: JON 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-07 16:07:04 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
late collections none

Description Viet Nguyen 2013-08-06 19:35:25 UTC
Created attachment 783474 [details]
late collections

I want to be able to tell what the current size of the late bucket is.

I believe  "Late Collection" metric shows cumulative value, ie total late collections to date. In order to tell if the agent is falling behind one will have to examine a larger range of data to determine whether late collections are flattening out or trending upward.

Comment 2 Jay Shaughnessy 2014-08-25 13:29:28 UTC
Is this a catch-22?  It may be hard to report that metric in a timely manner given that metric reporting is falling behind.  To report on agent load may require something special-case, like additional information sent with the ping or something like that.  Also, the agent log does, I believe, report when falling behind.  It could be useful to know, though, that the agent is overloaded.  But pushing out of 3.3 due to time and priority.

Comment 3 Filip Brychta 2019-03-07 16:07:04 UTC
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.