Bug 752207

Summary:	MeasurementCollectorRunner should log metric collections which fall behind at WARN instead of DEBUG
Product:	[Other] RHQ Project	Reporter:	Larry O'Leary <loleary>
Component:	Plugin Container	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	NEW ---	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.0.1	CC:	flo_bugzilla, hrupp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Description Larry O'Leary 2011-11-08 15:18:58 EST

Currently, when MeasurementCollectorRunner has requests which have a collection scheduled earlier then the current time minus 30 seconds, a debug log message is produced that looks like: "Measurement collection is falling behind... Missed requested time by [" + (System.currentTimeMillis() - requests.iterator().next().getNextCollection()) + "ms]"

(See http://git.fedorahosted.org/git?p=rhq/rhq.git;a=blob;f=modules/core/plugin-container/src/main/java/org/rhq/core/pc/measurement/MeasurementCollectorRunner.java;h=269f6266724f2ea17a771e0fb702d7abba5a0ae8;hb=release-3.0.1#l71)

Such a message seems like something that is potentially harmful or should be addressed and DEBUG level does not seem appropriate for this message. Can this be changed to WARN?

Comment 1 Heiko W. Rupp 2011-11-08 15:41:59 EST

Falling behind is an indication of overload (may be the agent, but also the target server), so this is definitively more important than just debug level.