Nagios served us well for three years, but with a growing number of servers (over 100) and the need for better graphs, we switched to Zabbix.
Why Not Nagios¶
Weak at trending and graphs. Text configuration for 100 servers = thousands of lines. No auto-discovery.
Zabbix Advantages¶
Templates — define once, assign to hosts. Auto-discovery of servers, filesystems, and interfaces. Graphs and dashboards out of the box.
Migration¶
Zabbix agent running in parallel with NRPE. Two weeks running both systems — verifying that Zabbix catches everything. Then switching alerting over.
JMX in Zabbix¶
Zabbix Java Gateway — native JMX monitoring. Template for GlassFish and Tomcat with pre-configured JMX items.
Conclusion¶
Zabbix is the better choice for us — visualization, templates, auto-discovery. Migration with a parallel run minimizes risk.
Need help with implementation?
Our experts can help with design, implementation, and operations. From architecture to production.
Contact us