Bug 734842 - Provide additional logging around drift detection
Summary: Provide additional logging around drift detection
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: John Sanda
QA Contact: Mike Foley
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-31 15:21 UTC by John Sanda
Modified: 2012-02-07 19:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-02-07 19:25:04 UTC

Attachments (Terms of Use)
agent log file which documents verification (1.16 MB, application/octet-stream)
2011-08-31 18:13 UTC, Mike Foley
no flags Details

Description John Sanda 2011-08-31 15:21:16 UTC
Description of problem:
We need to provide some additional logging around drift detection so that we can better see the following:

* when drift detection gets scheduled/requested
* when drift detection ends (as a result of a drift configuration be deleted)
* what is on the schedule queue

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 John Sanda 2011-08-31 16:58:12 UTC
I have added more detailed logging around the following:

* adding a schedule for a drift configuration
* removing a scheudle for a drift configuration
* updating a drift configuration for an existing schedule

Additional output is included when DEBUG is turned on. The agent logs will show what is in the schedule queue, and also report if it fails to update the queue. Failure to update the queue is reported with a WARN level so DEBUG is not required to see those statements.

commit hash: 5d4fbbefb4f9ee8767e3fb8e18c87a95bdd80d79

Comment 2 Mike Foley 2011-08-31 18:12:33 UTC
attaching agent log file, which documents the verification of this BZ.

Comment 3 Mike Foley 2011-08-31 18:13:14 UTC
Created attachment 520872 [details]
agent log file which documents verification

Comment 4 Mike Foley 2012-02-07 19:25:04 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE

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