Applies to: Omada SDN Controller v6.1 or later (including pre-release builds).

Context:
With the new Health Dashboard and device timelines in Omada Controller v6.1.x, the platform is becoming more “health-centric”, which is great. However, in MSP/MSSP and mission-critical environments, not all devices have the same operational impact.

A printer going offline is a minor ticket.A backup server, NAS, hypervisor, firewall, or core switch going offline is an incident.

Feature Request — “Critical Asset” Toggle: Please add a “Critical Asset” flag on the device/client details page.

Expected Behavior
1) Immediate Alerting: When a flagged device goes offline, trigger an immediate notification (push/email/webhook), bypassing non-critical notification intervals.

2) Visual Priority: Highlight/pin “Critical Assets” in the Clients list and in the Health Dashboard (e.g., icon + filter + priority view).

3) Optional Thresholds / Anti-noise Controls: Allow a short offline threshold (e.g., 10–30 seconds) and maintenance windows, to avoid false positives during planned changes.

Business Value

This would significantly reduce MTTR and help maintain stricter SLAs without requiring a full third-party NMS for smaller deployments.