Under some circumstances you may want to suppress alerts such as during the scheduled maintenance times or the holiday time. Prognosis provides multiple ways to suppressing alerts:
Individual Threshold Condition’s Timing Tab (Note, this tab overwrites the Threshold's Schedule tab.)
To suppress alerts from all thresholds, enable the following statement in ALERTS Configuration:
Note, all the thresholds are still running but won't trigger any alerts. The benefit of this statement is to suppress alerts without stopping all thresholds. Stopping all thresholds can stop the alerts but you will have to manually start the thresholds when the maintenance window is over.
Also note, the SCHEDULE configuration does NOT suppress any alerts. It is only used for Availability monitoring, ie, the downtime in the scheduled time will not be counted into the Availability.
This is for individual condition only.
This is for individual rule only.
This is for SNMP trap alert only.
Suppress alerts for particular customers for enahnced Prognosis Alerts.
This is good if you want to supress alerts for one threshold type for all devices. However, I would like to supress alerts for a single device which is one of a couple of hundred devices monitored by the same threshold. For example, I have a couple hundred Cisco routers acting as voice gateways. I have one site that is in maintenance, so I would like to supress the alerts for that single router. If I stop or supress monitoring for the entire threshold (say the IptDeviceTh threshold or even the PSTNGatewayUnreachable condition) it stops it for ALL of my devices and not just the one. How do I easily supress alerts for just a single device? In tools such as SolarWinds I simply find my device and click a button to supress all alerts for it.
If you're alerting via RabbitMQ, you can use the alert suppression mechanism in the WebUI. This would allow you to suppress alerts at the device level. This does require additional licensing and configuration to set up and is described in more detail here.
For all other alerting, the only way I can suggest is to filter the specific device out by modifying the where clause.
For example, the PSTNGatewayDown condition uses a default where clause of 'DEVSTATE = 3'.
To prevent that condition from generating an alert for a specific device called SYD-RTR01, you would change the where clause on that condition to 'DEVSTATE = 3 AND DEVNAME NOT CONTAINS "SYD-RTR01"'.
I would recommend creating a display that uses the DEVPSGW record as this will allow you to identify exactly what the DEVNAME is for the device you don't want alerts from.
Of course, you would also need to remember to remove this additional filter when that device was brought back online.
I hope this helps, but please let us know if you have any additional questions!
Unified Communications has always been an important part of companies' digital transformation efforts due to its ability to enable rich virtual collaboration and communication. But with COVID-19, we've reached a break-through point.
Join Bill Haskins, Sr. Analyst & Partner, Unified Communications at Wainhouse Research, and John Ruthven, CEO at IR discuss UC challenges companies are experiencing due to the COVOID-19 crisis.Join webinar