+++ This bug was initially created as a clone of Bug #829962 +++ This needs to be in the JON docs - FAQ, somewhere. http://rhq-project.org/display/JOPR2/FAQ#FAQ-IcreatedanalertdefinitionandIknowimmediatelythereaftermyagentshouldhavereporteddatathatshouldhavetriggeredthealertbutmyalertdidnotfire.Wheredidmyalertgo%3F "Q: I created an alert definition and I know immediately thereafter my agent should have reported data that should have triggered the alert - but my alert did not fire. Where did my alert go? A: When you create your alert definitions, you will need to wait a short amount of time before that alert definition makes its way into the RHQ Servers' alert caches throughout the RHQ HA Server cloud (and when it does, then it will be able to fire alerts). This small window of time between the creation of your alert definition and when it starts firing alerts is roughly around 30 seconds, give or take a few seconds. To be safe, assume you should wait over a minute."
Add this to the end of that FAQ entry as well: --- You will know the alert def made it into the cache and is ready to fire alerts when the RHQ Server logs messages like this: INFO [CacheConsistencyManagerBean] localhost took [51]ms to reload global cache INFO [CacheConsistencyManagerBean] localhost took [49]ms to reload cache for 1 agents
I added a thing on troubleshooting alerts: http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/Admin_Setting_up_Monitoring_Alerts_and_Operations/alert-data.html#alerts-trouble And it's in the FAQ: http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/Frequently_Asked_Questions/index.html#id2738526
verified.