Home: http://www.zabbix.com/

Downloads: http://www.zabbix.com/download.php

Documentation: https://www.zabbix.com/documentation/2.4/manual/installation/requirements

Wiki: http://www.zabbix.org/wiki

Forums: https://www.zabbix.com/forum/

HowTo - Server: http://tecadmin.net/install-zabbix-on-ubuntu/

HowTo - Agent: http://tecadmin.net/install-zabbix-agent-on-centos-rhel/

See also zabbix

http://tecadmin.net/add-host-zabbix-server-monitor/

https://www.zabbix.com/documentation/2.4/manual/config/hosts/host

https://www.zabbix.com/forum/showthread.php?t=19921

Use Case: You have a monitored device on a circuit that is having issues. Rather than have constant alerts due to packet loss etc. modify the alert to minimize the churning until the circuit can be stabilized then return to the stock template.

• Clone the template with the problem alert. Use “Full Clone” to take advantage of the previous configuration.

https://www.zabbix.com/documentation/2.4/manual/config/templates/template

• Create the problem alert

https://www.zabbix.com/documentation/2.4/manual/config/triggers/dependencies

Sometimes the availability of one host depends on another. A server that is behind some router will become unreachable if the router goes down. With triggers configured for both, you might get notifications about two hosts down - while only the router was the guilty party.