Currently, Huntress applies global thresholds for "Protected" and "Unresponsive" statuses across all organization assets. This "one-size-fits-all" approach creates a conflict between high-availability assets (Servers) and general use devices (Workstations).

Workstations: Users on vacation or long weekends frequently trigger "Unresponsive" alerts, leading to alert fatigue.

Servers: If thresholds are loosened to accommodate workstations, a critical server could be offline for days before the dashboard reflects an actionable "Unresponsive" state.

Having some sort of asset based status threshold that allows us to define different "Unresponsive" and "Protected" timeframes based on the asset type or a specific tag.

Something like logic that automatically applies tighter thresholds (i.e., 1 - 4 hours) to assets detected as Server OS (or tagged as a server via tags), while maintaining a longer grace period (i.e., 3 - 5 days) for non tagged or non Server OS devices.