FYI. I have noticed some unexplained behaviour when a node is Unmanaged. It seems the IP address is still pinged and there is some snmp activity.
A down and unmanaged device fails those pings and this puts the node into the Top 10 Nodes by Packet Loss resource.
A node that was shutdown last week (and unmanaged) still shows its last interface traffic stats under Maximum Traffic Today.
If the unmanaged device still exists it is quietly replying to those pings, though it now appears in the Down Nodes resource.
It still shows it's Availability Statistics, ie 100.00% Availability for the last 30 days
It still appears to be re-discovered on schedule and Database Updated (according to Polling Details).
I know the unmanaged devices can be filtered out of the various displays but it seems the underlying behaviour could be tidied up.
As a further test I unmanaged an unimportant but reliable switch.
The Average Response Time & Packet Loss Gauges remain on the page and are active (but chart details look suspended), CPU Load & Memory Utilisation Gauges have disappeared from the page. After a while I changed the snmp string (made it incorrect) for this device and immediately saw 3 authenticationFailure Traps appear for the device. There were further authenticationFailure Traps which correspond with times of the scheduled (but thought to be unmanaged) rediscovery process. I corrected the snmp string (no traps this time) and remanaged the node.
Lastly, in the Overview View, the icon to indicate the unmanaged node, blue with cross, does not appear in the legend with the other LEDs.
Interesting that Interfaces are indicated here as unmanaged, though technically that is only an inherited condition of the Node being unmanaged.
If an interface COULD be unmanaged (like so many have requested) or alerts and events suppressed while stats are silently collected as above, then you really would have a winner.
evaluating ver 9.1