Bug 734246

Summary:	Publish performance stat attributes for the Collector
Product:	Red Hat Enterprise MRG	Reporter:	Erik Erlandson <eerlands>
Component:	condor	Assignee:	grid-maint-list <grid-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.0	CC:	ltoscano, matt, mkudlej, tstclair
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-26 20:22:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Erik Erlandson 2011-08-29 21:12:01 UTC

Description of problem:
Publish some performance statistics on the collector ad to aid in determining if the collector is performing well or is overworked. Analogous to the recent performance statistics enhancements for the negotiator and scheduler ads.

Suggested performance statistics so far are:

WindowedStatWidth -- value of COLLECTOR.WINDOWED_STAT_WIDTH (see #2006)
CollectorUpdates -- updates over most recent time window WindowedStatWidth
CollectorUpdateRate -- update rate over the previous time window, defined by WindowedStatwidth
CollectorUpdatesCumulative updates over collector lifetime

EventLoopLoad -- 0% to 100% (or 0 to 1).  What fraction of time in event loop is non-idle.  (look into properly accounting for time spent in select())  (is this also over WindowedStatWidth?)
EventLoopLoadCumulative -- load over collector lifetime


Additional info:
upstream: https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=2211

Comment 3 Anne-Louise Tangring 2016-05-26 20:22:58 UTC

MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.