Line 300: |
Line 300: |
| *'''status''': (enabled|disabled) Should the service be starte dautomatically | | *'''status''': (enabled|disabled) Should the service be starte dautomatically |
| | | |
− | === Monitoring zabbix server === | + | === Monitoring SME servers === |
| | | |
− | If you installed zabbix-server on your SME, you'll certainly want to monitor itself. For this, you'll have to install zabbix-agent, and configure it to send reports on localhost: | + | If you want to monitor SME Servers with zabbix, you'll first need to install the agent as explained earlier, then |
− | yum --enablerepo=smecontribs install smeserver-zabbix-agent
| + | configure the agent to send informations to your server. For example, to monitor you local server (the one running zabbix-server): |
| db configuration setprop zabbix-agent Servers localhost | | db configuration setprop zabbix-agent Servers localhost |
| signal-event zabbix-agent-update | | signal-event zabbix-agent-update |
| + | |
| | | |
| Then, just add a host in zabbix, pointing to localhost. Remember, the default mode for the agent is active mode only, so you'll have to name this new host <hostname>.<domain.tld>, then enter 127.0.0.1 in the IP address field. | | Then, just add a host in zabbix, pointing to localhost. Remember, the default mode for the agent is active mode only, so you'll have to name this new host <hostname>.<domain.tld>, then enter 127.0.0.1 in the IP address field. |
| | | |
| Now you can start adding items (type agent (active)) to this new host. | | Now you can start adding items (type agent (active)) to this new host. |
| + | |
| + | You can download [http://sme.firewall-services.com/downloads/zabbix/zabbix_SME.xml.zip here] an XML export of the templates I use to monitor some servers. Just extract the archive, and import it in zabbix (using the Import/Export menu of zabbix configuration) |
| + | It'll create some new templates in zabbix: |
| + | |
| + | *Template_SME is for agents running in active mode (default of the contrib) |
| + | *Template_SME_dynip is for agents running in passive mode (I use it to monitor SME Servers with a dynamic IP address) |
| + | |
| + | If you use one of this template, it'll configure a lot of items, graphs, triggers. Of course, you'll need to adjust it to your needs. |
| + | |
| + | Those two templates are based on other templates you can use for other hosts (non SME): |
| + | *Template_all uses only icmp checks. It'll enable latency graphs and triggers if latency is too high or if the host is down |
| + | *Template_nutUPS can monitor the status of your UPS. It needs the UserParameters ups.load ups.battery.charge ups.status and ups.model which are allready configured on the agent on SME. |
| | | |
| === Bugs === | | === Bugs === |