You can control which events generate emails from the Event Management page on the SZ GUI
To enable or disable email option per event, highlight the event and hit enable or disable pull down menu
AP disconnection is preceded by AP heartbeat errors (314) then AP disconnect (303) and then reconnect (312). You may also be receiving a change of control plane event if you have multiple nodes cluster (311). You can determine which of these messages are important enough to notify you by email.
DB persistence determines if the event is stored in the SZ.
This is a start. But it would be great to have a throttling mechanism (or a bundling mechanism to collapse multiple alerts to a single email). For example, with a power failure, multiple APs will go down all simultaneously (or withing one keep-alive lifetime of each other)... it would be great to condense this to a single message. Because today i still would like to receive emails for an event (like an AP going down) but at the same time, I can be bombarded with hundreds of messages when there is a power failure.
Hi Albert, thanks for the reply. Can we also modify the threshold set for a certain alert/alarm code. We need a way to adjust the threshold of the alerts. If not, atleast adjust the threshold before an email is sent for an alert.
For example, Threshold of the alerts - AP disconnected after 15 minutes of no heartbeat. Threshold of emails - email only after AP disconnected alert has been active for 15 minutes