Prognosis Foundation 10.3.0 - Alerts - Not Working as Expected

[Marlon]

Last night, we had a 3 hour outage on 2 of our circuits. When I checked this morning, Prognosis shows that the circuit's last state was down around the time the circuits came back online.

Our Avaya CM 5.2 PBX is the only configured device on our installation of Prognosis and notifications is enabled. We have received notifications before, but it seems they are inconsistent or has to be at least 5 minutes into a status change before Prognosis reflects the issue.

Has anyone any idea as to why this would be occurring and if there is any way to test notifications without purposely causing an outage situation?

[GeraldC]

Hi Marlon
One thought is, the alerts rely on the PBX responding to and giving Prognosis the current status. Depending on the specifics there are ways to alert if last response was a long time ago, if the SAT connection was disconnected, if no ping reply, things like that. Theoretically, testing might involve finding a manually changeable setting on the PBX that has no impact and then making Prognosis alert on it.

If you open a case with IR Support they can assist you to consider the specifics of that particular alert.

HTH

[GeraldC]

Hi Marlon

Another thing, the out-of-box Avaya_Alerts in recent versions does have some smarts built in. Here's an example:
HTH

Avaya_Alert :\MYPBX SAT connection lost
No information was available for AvayaDS1Board. The query was successful, but no rows were returned.
This PBX has the following TrunkGroups
Unable to retrieve data for component AvayaTrunkGroup