Bug 872185 - Traceability of particular measurements in agent's log
Traceability of particular measurements in agent's log
Product: RHQ Project
Classification: Other
Component: Plugin Container (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: ---
: RHQ 4.6
Assigned To: Jirka Kremser
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2012-11-01 09:46 EDT by Jirka Kremser
Modified: 2013-09-03 10:45 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-03 10:45:57 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jirka Kremser 2012-11-01 09:46:46 EDT
Description of problem:
Now, it is logged when the MeasurementFacet.getValues() takes longer than 2s. When TRACE log level is turned on, it should be possible to find all the measurements in the agent's log to help to find out what is exactly happening.

Version-Release number of selected component (if applicable):

How reproducible:
Comment 1 Jirka Kremser 2012-11-01 11:01:01 EDT

fixed in master
time:    Thu Nov 1 15:54:18 2012 +0100
commit:  ce0f7f28d85bd4fbd23b6969499715ae8a28a6e6
author:  Jirka Kremser - jkremser@redhat.com
message: [BZ 872185 - Traceability of particular measurements in agent's log] If TRACE log lvl is enabled, each measurement is logged into the agent's log
Comment 2 Heiko W. Rupp 2013-09-03 10:45:57 EDT
Bulk closing of issues in old RHQ releases that are in production for a while now.

Please open a new issue when running into an issue.

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