E-Mailed Alarm Notifications are too slow

• ZD and AP expect hearbeat (echo) requests or responses in 40 and 30 seconds respectively. If no ZD and AP would consider the heartbeat is lost. 
  
• ZD side
•  After 2 consecutive (80 seconds) heartbeat losses, ZD raises an "heartbeats lost" alert and delete the AP.
•  After another 20 minutes, if AP does not discover and join ZD, ZD raises "Lost contact to AP" alert.
• AP side
• After a heartbeat lost (30 seconds),  AP sends 12 consecutive heartbeat requests every 5 seconds (total 60 seconds).  If still does not hear response from ZD, AP enters Sole Run state and starts to send discovery request.
• In Sole Run state, AP sends out discovery request every 5 seconds for 15 minutes.  After receiving no responses, AP will reboot and leave a reboot reason viewable in support text stating "can not discover ZD in 180 attempts".

I run a high school campus network with 1400 students. When an AP goes offline, it potentially affects multiple classrooms. So quick notification of that event is paramount to our MIS Dept providing outstanding service; we are on this before they even know!

My Xirrus array central management console sends me alerts within seconds of an outage. My intention is to replace over twenty Xirrus AP's with Ruckus devices however this glaring weakness in the reporting function is making me re-think this decision. I urge you to consider this a feature request. This is pretty important to us.

thanks,

Sheldon