Fairly recently I started receiving Alerts for Virtual Memory for a handful of (VeloCloud) Nodes that were being polled via SNMP.
I've since remove 'Virtual Memory' and 'Physical memory' from the Resources list, but found that Solarwinds is still Alerting, apparently based on data that had been collected previously (before I removed the two resources).
I would have assumed that when the Resources were removed, alerting would no longer be active for those Resources.
My Idea, then, would be to either: 1) Don't Alert and/or Display Node (or Child) status based on Resources that are not being monitored or 2) Remove the old collected data from the database when a Node's Resources were removed.
Ref: Case # 00801305 - Alert still fires even though Specific Resource in no longer monitored