Bug 534281 (RHQ-1092)
Summary: | be able to configure the availability "quiet time" before backfilling | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | John Mazzitelli <mazz> |
Component: | Monitoring | Assignee: | John Mazzitelli <mazz> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Corey Welton <cwelton> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | Keywords: | Improvement |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://jira.rhq-project.org/browse/RHQ-1092 | ||
Whiteboard: | |||
Fixed In Version: | 1.2 | Doc Type: | Enhancement |
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: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 534286 | ||
Bug Blocks: |
Description
John Mazzitelli
2008-11-09 00:30:00 UTC
An alternative is to perform some additional checking after 2 minutes of quiet time but before we actually backfill. Perhaps we can look in our DB for ANY activity from the agent right before we backfill. If we've seen we already processed (within the past 2 minutes) an inventory report, a measurement report, an operation result, a configuration change or other agent-originating message, we can assume the agent is up and just hasn't been able to send us its avail report yet. In this case, we abort the backfill. So its: 1) checkSuspectAgents looks for an avail report that occurred within the past 2 minutes. If nothing then: 2) check to see if the agent has sent us any message in the previous 2m interval (like inventory report, measurement report, operation result, etc). If we DID get such a message from the agent, abort and do not backfill. Otherwise: 3) continue with the normal backfill processing So step 2) would be new. making this critical - we need to at least explore the possibilty to bump up the quiet time interval and avail report interval. Admin > Server Config page now allows you to specify the agent max quiet time allowed setting which is what our check-suspect-agent job will use. therefore, this setting takes affect across the cloud. we no longer support that hidden system property override . QA Verified. This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1092 This bug relates to RHQ-1303 Mass move to component= Monitoring |