So far, as mentioned earlier, we have been able to provide graphs on at least 292000 operational ports spread across more than 27,000 devices. Each port has IN traffic, OUT traffic, ping packet drops and round trip latency,  Enigma automatically begins monitoring interfaces that are up and active. There are a few different factors involved. This is not really very configurable (you can enable them manually but disabling them once they are enabled is still kind of sketchy last time I checked), but it works well enough by itself that it requires little to no maintenance. 

Environment monitors are handled by different code than the interface monitors (in CentOS, you can see all the different scripts that are run through a Linux cron job), which means that they are logically separated to a certain extent, but are pretty well integrated into the GUI. 

For example, I gather that NETSAS has a difficult time relating database objects in the direction of Environment Monitor-TO-Device, which is, I believe, why we still don’t have the dynamic grouping feature I mentioned earlier. But when viewing an individual device, you can easily view all the Environment Monitors related to it.

If you are going to have a lot of devices being added and removed to/from a monitoring system daily, you need one with an API so that you don't have to manually do all of it. I did it manually for a while and then later handed it off to our IP provisioning team, but now Enigma has a REST API, and it works fairly well and has decent instructions. One difficulty I had while working with it was that both the node name and the node IP must be unique in the entire database. This makes it difficult sometimes to correct the name of one node if its IP has been reassigned to another device. I had to write a lot of code to work around this, and in the process I ended up switching from a real-time one-off solution to a scheduled audit solution.