Changes

From SME Server
Jump to navigationJump to search
1,109 bytes added ,  20:45, 31 March 2009
New templates
Line 322: Line 322:  
=== Monitoring SME servers ===
 
=== Monitoring SME servers ===
   −
If you want to monitor SME Servers with zabbix, you'll first need to install the agent as explained earlier, then  
+
If you want to monitor SME Servers with zabbix, you'll first need to install the agent as explained earlier, then configure the agent to accept connection from your server. For example, to monitor you local server (the one running zabbix-server):
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 active disabled passive enabled
 +
signal-event zabbix-agent-update
 +
 
 +
{{Note box|After installation, the agent is configured for active checks only. Here, we disable the active checks, and enable the passive ones.}}
 +
 
 +
Then, just add a host in Zabbix, pointing to localhost. Remember, if you use the active mode (agent send informations to the server), so you'll have to name the host <hostname>.<domain.tld>, then enter 127.0.0.1 in the IP address field.
 +
 
 +
Now you can start adding items (type agent (active or passive depending on the mode you use on the agent)) to this new host.
 +
 
 +
If you want to monitor SME Servers on the Internet and use passive mode, the server will initiate connections to the agent. You'll need to port-forward the port if you run in serveronly mode (the default is port 10050 TCP), or to open this port in the firewall if runing in server&gateway mode:
 +
 
 +
db configuration setprop zabbix-agent Servers w.x.y.z active disabled passive enabled access public AllowHosts w.x.y.z
 
  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.
+
You can download [http://sme.firewall-services.com/downloads/zabbix/zabbix_SME.zip here] an archive with some XML exports of the templates I use to monitor my servers. Just extract the archive, and import the templates you want in Zabbix (using the Import/Export menu of zabbix configuration)
 +
 
 +
Each XML file represent a template in Zabbix
   −
Now you can start adding items (type agent (active)) to this new host.
+
*'''Template_SME''' is the main template. It'll add a lot of items for global system monitoring, triggers if load is too high, lack of free memory, httpd is down, passwd has changed etc... and also some graphs like CPU usage, memory, disk space, network usage etc... This templates requires the '''Template_icmp''' and '''Template_app_MySQL''' template
   −
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)
+
*'''Template_SME_coovaChilli''' will add tun0 statistics (useful if you use [[CoovaChilli]] contrib). It'll also create a graph for tun0 stats
It'll create some new templates in zabbix:
     −
*Template_SME is for agents running in active mode (default of the contrib)
+
*'''Template_SME_softRaid''' will add items and triggers for software raid monitoring. If you link a SME Server with this template, you'll be warned if one of the raid array is degraded or rebuilding
*Template_SME_dynip is for agents running in passive mode (I use it to monitor SME Servers with a dynamic IP address)
  −
*Template_SME_hostpot will add tun0 statistics (useful if you use [[CoovaChilli]] contrib)
     −
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.
+
*'''Template_SME_megaRaid''' will do the same but for MegaRaid based cards. It also requires the MegaCli utility from [http://www.lsi.com/storage_home/products_home/internal_raid/megaraid_sas/ LSI] website
   −
Templates '''Template_SME''' and '''Template_SME_dynip''' are based on other templates you can use for other hosts (non SME):
+
*'''Template_SME_nutUPS''': Will add items and triggers to be warned if your UPS is on battery, or overloaded.
*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 already configured on the agent on SME.
  −
*Template_app_MySQL: reports MySQL statistics
      +
*'''Template_icmp''': will configure two items to check if the server is alive, and measure the latency. It also provides latency graphs and some triggers (if latency is too high, if host is down since more than 5min and if hosts is down for more than 1 hour)
    
=== Bugs ===
 
=== Bugs ===

Navigation menu