Enigma NMS Pros
Enigma still does not have all the features we want, but it has enough of the most desired features: scalability, notifications, custom OIDs, good graphs, small polling interval, long term data retention, single poller.
Enigma has a lot of specific detail coded into it for discovering and monitoring Cisco devices. If you are a Cisco shop this might be a major consideration.
So far, as mentioned earlier, we have been able to provide graphs on at least 80,000 metrics spread across more than 10,000 devices. Enigma automatically begins monitoring interfaces that are up and active. There are a few different factors involved. This is not really configurable, but it works well enough by itself that it requires little to no maintenance.View full review »
Enigma NMS Cons
We would like to see more flexibility with alerting. Since our adoption of Enigma, it has improved greatly in this area, but there are still alerting threshold configurability limitations that we would like to see improvements on.
I would like to see dynamic grouping. For example, in our case, we have Subscriber Units that are connected to APs. These are constantly being re-homed, or pointed to a different AP on the same tower or a different tower altogether. There is an SNMP value corresponding to the AP name, and one for the AP MAC address. I would like Enigma to be able to form groups based on the AP name (or the MAC address, either one), which are dynamically changed.
I would also like to see Enigma move away from CentOS 6.5 and onto a more current platform, as well as away from myISAM tables to InnoDB. No improvements are being made to myISAM, and this has been the case for several years, from what I understand. So, this code is going to become more and more outdated by that virtue alone. The developers say that myISAM tables are faster. I did some reading up on it, and it seems that at one point, when InnoDB was new, it was slower than myISAM, but InnoDB has made major improvements since then.View full review »