Bug 749670 - can the user know more easily when an agent's local time has skewed too far from the server's time?
can the user know more easily when an agent's local time has skewed too far f...
Status: NEW
Product: RHQ Project
Classification: Other
Component: Agent (Show other bugs)
Unspecified Unspecified
medium Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2011-10-27 16:33 EDT by John Mazzitelli
Modified: 2011-10-31 11:31 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
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 John Mazzitelli 2011-10-27 16:33:12 EDT
When the agent detects that its local time has skewed "too far" from its server's time, it logs that in the agent log. There is also a metric that tracks the time difference.

How can we get the user to know more easily that this happened?

There are several ways to do this - but require manual setup:

a) user can create an alert definition/template so an alert is triggered when the time difference is over a certain amount

b) the user can enable event log tracking on the agent and have an alert def to trigger when the log warning is dumped by the agent

We could add the ability to send up a resource error to the server so the server can show the yellow warning icon on the RHQ Agent resource view. The agent should probably not send up too many of these resource errors - maybe only do it every hour or so?

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