This means that a total of seven alerts were detected by VizAlerts on the entire Server, but it was not time to run any of them, according to their Schedule. If it keeps reporting that after the Schedules were set to run, then there's likely an issue with the Schedule settings.
Alerts-Daily is scheduled to run @ 6:00AM, but we are testing it, so we added comments 'test_alerts' and then re-ran the yams script, but no email.We d have data in our reports.
The Windows Task scheduler is running every 15mins.
Am I missing anything?
Okay, that explains it. Two things:
1. The comment must be "test_alert" (exactly) and must be entered by the owner of the viz. Any comments entered by a non-owner will be ignored.
2. VizAlerts will pick up the ad-hoc test request after its second iteration (the first logs the existence of the alert, the second detects that it is time to run it). This is one reason that we recommend running VizAlerts every minute, as you'll now be waiting up to 30 minutes for your test results.
1.Sorry the comment is test_alert (s) was a typo.
So I enter the comment and wait but nothing...we have tried couple of times but no emails.We have waited for more than 2 hrs and nothing.
Is there a particular thing we should be looking at?
Thanks for your prompt response.
Ah yes, I just realized, the time limit for when the comment method is picked up is 5 minutes. So if you aren't executing VizAlerts twice in that timeframe, it won't know to send the email. High level, run it every minute and you'll solve a multitude of problems. It should not take up much resources to do so, all it does is run the query in vizalerts.yaml against the PostgreSQL repository and generate a test trusted ticket. Both very light operations. The only real work that it asks Server to do is when your alerts actually get triggered.
Were you able to test whether the increased run cadence fixed your issue, Shelly?
Ahh..yes, It did.
Thank you again for your prompt help!
Thanks for the follow-up! You're welcome.