Bug 752207 - MeasurementCollectorRunner should log metric collections which fall behind at WARN instead of DEBUG
MeasurementCollectorRunner should log metric collections which fall behind at...
Status: NEW
Product: RHQ Project
Classification: Other
Component: Plugin Container (Show other bugs)
3.0.1
Unspecified Unspecified
medium Severity low (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-08 15:18 EST by Larry O'Leary
Modified: 2011-12-01 15:12 EST (History)
2 users (show)

See Also:
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: ---


Attachments (Terms of Use)

  None (edit)
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.

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