Hi Laszlo,
Nothing has changed on the sending of alerts.
You can force sending an alert or recovery notice with ./test_alert.php -a <alert_id>
The alert_id is the id on the page with the alert entry availability graphs (click the cog on the right hand side of the alert table entry)
If you also use -d, you'll get some debugging output.
Thanks, adam. On 10/08/2016 09:01:50, Laszlo Nemeth laszlo.nemeth@emarsys.com wrote: Hello,
At the morning I was on the 7933 but 2 hours ago I updated to 8039.
I used a CPU alert for my routers. In the older version it is worked, I got the alerts via mail and PagerDuty as I set up.
Now after the upgrade I would like to test the alerting because on 7933 i “pached” the pagerduty.inc.php for more info in the PD message (the default file just send like “something wrong somewhere” :)
So. After the upgrade with the original (nor pached) PD file I would like a test to see how looks out a PD message now. I set a lower value for the CPU alerting (from 50% to 15%) to generate alerting (now the cpu load is 18-25%)
After a few minutes I see in the Alers / Processor that my deviced appear and show that the status is FAILED. It is ok. In the Alert Logging I get the “Checks failed” so it is great.
But. I never get “Alert notification sent” messages. (I get “Alert notification sent” for other events, so the alerting is working for other services).
I see in the Alerts that the router’s status is Failed, Checked 18s Changed 20m 36s, Alerted: never.
What I have to do for send the alerts? Or for the debug?
Thanks
BR Laszlo
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium