665
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 23:
Line 23: − + Line 45:
Line 45: − + Line 127:
Line 127: − − *All Information is Available Online − ** ZABBIX Manual − ** ZABBIX Forums − ** ZABBIX Wiki − − *Backed by ZABBIX Company − ** Annual support agreements − ** Turn-key solutions − ** Technical Account Manager − ** Professional Services Line 144:
Line 133: − + Line 172:
Line 161: − + Line 191:
Line 180: − + Line 208:
Line 197: − + Line 246:
Line 235: − + Line 253:
Line 242: − + − + Line 263:
Line 252: − + Line 297:
Line 286: − + Line 323:
Line 312: − + − + Line 335:
Line 324: − + − + − + − + − + − +
Cleanup, typos
*Scalability
*Scalability
** Tested with 10,000 monitored devices and servers
** Tested with 10,000 monitored devices and servers
** Tested with 100,000 availability and perfomance checks
** Tested with 100,000 availability and performance checks
** Processing of thousands of availability and performance checks per second
** Processing of thousands of availability and performance checks per second
*Assuring SLA
*Assuring SLA
** Hierarchial IT Services
** Hierarchical IT Services
** Real-time SLA reporting
** Real-time SLA reporting
** All data is stored in a database (Oracle, MySQL, PostgreSQL, SQLite)
** All data is stored in a database (Oracle, MySQL, PostgreSQL, SQLite)
** Centralised configuration and storage of information
** Centralised configuration and storage of information
*and more...
*and more...
This wiki page is not a complete guide for Zabbix, but just a starting point to run it on your SME Server using this contrib.
This wiki page is not a complete guide for Zabbix, but just a starting point to run it on your SME Server using this contrib.
For a complete documentation, please refere to the project documentation: http://www.zabbix.com/documentation.php
For a complete documentation, please refer to the project documentation: http://www.zabbix.com/documentation.php
=== Versions ===
=== Versions ===
==== Server ====
==== Server ====
The server is the core component of Zabbix software. It uses one database (MySQL in this contrib) to store configuration, performance and integrity informations. The server can check network services with simple check (icmp, tcp etc...) for agent-less monitoring, it can monitor network devices using snmp and is also the central component to which agent report informations (agent can work in active, passive, or both mode). The server will also analyze all the informations and send alerts depending on very flexible triggers.
The server is the core component of Zabbix software. It uses one database (MySQL in this contrib) to store configuration, performance and integrity informations. The server can check network services with simple check (ICMP, TCP etc...) for agent-less monitoring, it can monitor network devices using SNMP and is also the central component to which agent report informations (agent can work in active, passive, or both mode). The server will also analyse all the informations and send alerts depending on very flexible triggers.
===== Installation =====
===== Installation =====
{{Note box|The different Jabber settings above are not for the built-in jabber notification function (because I couldn't get it working as my server requires TLS and the built-in feature do not support it). But I've included a external script using sendxmpp to send the notification. You should have a media called 'xmpp' in zabbix administration. }}
{{Note box|The different Jabber settings above are not for the built-in jabber notification function (because I couldn't get it working as my server requires TLS and the built-in feature do not support it). But I've included a external script using sendxmpp to send the notification. You should have a media called 'xmpp' in zabbix administration. }}
*'''NodeID''': The node ID of your server. If you don't use ditributed monitoring (just one central zabbix server), you should let this to 0
*'''NodeID''': The node ID of your server. If you don't use distributed monitoring (just one central Zabbix server), you should let this to 0
*'''TCPPort''': Port used for agent<->server (and proxy<->server) communication. The default is 10051
*'''TCPPort''': Port used for agent<->server (and proxy<->server) communication. The default is 10051
*'''TimeZone''': It's very important for zabbix to know your time zone (PHP TimeZone setting). Unfortunately, SME do not set it. You can specify your time zone. This setting will only affect Zabbix
*'''TimeZone''': It's very important for zabbix to know your time zone (PHP TimeZone setting). Unfortunately, SME do not set it. You can specify your time zone. This setting will only affect Zabbix
The main web interface is available (if not disabled with teh key WebAccess) on https://server.domain.tld/zabbix.
The main web interface is available (if not disabled with teh key WebAccess) on https://server.domain.tld/zabbix.
The default user is admin, with password 'zabbix' (you should change this password ASAP)
The default user is '''admin''', with password '''zabbix''' (you should change this password ASAP)
Here are some screenshots of what you can get with zabbix
Here are some screenshots of what you can get with zabbix
*'''Servers''': List of servers (or proxy), separated by commas, to which send informations. The first one may be used for active checks, the others are only for passive mode
*'''Servers''': List of servers (or proxy), separated by commas, to which send informations. The first one may be used for active checks, the others are only for passive mode
*'''TCPPort''': TCP port on which the agent will listen if passive mode is enabled
*'''TCPPort''': TCP port on which the agent will listen if passive mode is enabled
*'''access''': (public|private) If you want to open the agent on the public interface (only usefull if passive is enabled). If you set this to 'public' you should use the AllowHost key to limit the access
*'''access''': (public|private) If you want to open the agent on the public interface (only useful if passive is enabled). If you set this to 'public' you should use the AllowHost key to limit the access
*'''active''': (enabled|disabled) Do you want to enabled the active mode
*'''active''': (enabled|disabled) Do you want to enabled the active mode
*'''passvie''': (enabled|disabled) Do you want to enable the passive mode
*'''passvie''': (enabled|disabled) Do you want to enable the passive mode
===== Additional checks =====
===== Additional checks =====
Even if zabbix agent is great and support natively a lot of checks, some were missing for my use, so I've added some UserParameters entries in the configuration file. For each of this check, you should add a new item with the name of the check as the key.
Even if Zabbix agent is great and support natively a lot of checks, some were missing for my use, so I've added some UserParameters entries in the configuration file. For each of this check, you should add a new item with the name of the check as the key.
Configuring the corresponding checks on the server can be quite long. You can have a look at the [http://sme.firewall-services.com/downloads/zabbix/zabbix_SME.xml.zip templates] I use to monitor SME Servers. This file is an XML export of my templates. You can use the Import/Export functionality of zabbix (Manual Chap. 8.XML IMPORT AND EXPORT page 154) to import it on your server.
Configuring the corresponding checks on the server can be quite long. You can have a look at the [http://sme.firewall-services.com/downloads/zabbix/zabbix_SME.xml.zip templates] I use to monitor SME Servers. This file is an XML export of my templates. You can use the Import/Export functionality of Zabbix (Manual Chap. 8.XML IMPORT AND EXPORT page 154) to import it on your server.
You can also have a look at the configuration file /etc/zabbix/zabbix_agentd.conf (at the end of the file) to see the commands used to return the corresponding values.
You can also have a look at the configuration file /etc/zabbix/zabbix_agentd.conf (at the end of the file) to see the commands used to return the corresponding values.
**'''ip.external''': Return the real external IP address.
**'''ip.external''': Return the real external IP address.
*Incomming mails statistics:
*Incoming mails statistics:
**'''mail.in.denied.dnsbl''': number of emails rejected by DNSBL since the last run
**'''mail.in.denied.dnsbl''': number of emails rejected by DNSBL since the last run
**'''mail.in.denied.rhsbl''': number of emails rejected by RHSBL since the last run
**'''mail.in.denied.rhsbl''': number of emails rejected by RHSBL since the last run
**'''mysql.size''': total space used by mysql databases
**'''mysql.size''': total space used by mysql databases
*Network usage. These checks are usefull if you want to monitor several SME Servers using one template (so same checks), but those servers use different interfaces configuration (eth0, eth1, br0, bond0, ppp0 etc...)
*Network usage. These checks are useful if you want to monitor several SME Servers using one template (so same checks), but those servers use different interfaces configuration (eth0, eth1, br0, bond0, ppp0 etc...)
**'''net.if.in.internal''': Equivalent to net.if.in[ethX,bytes], but is independent of your internal interface name (eth0, bond0, br0 etc...)
**'''net.if.in.internal''': Equivalent to net.if.in[ethX,bytes], but is independent of your internal interface name (eth0, bond0, br0 etc...)
**'''net.if.out.internal''': Equivalent to net.if.out[ethX,bytes]
**'''net.if.out.internal''': Equivalent to net.if.out[ethX,bytes]
*'''DbUser''': the user to access the database
*'''DbUser''': the user to access the database
*'''Servers''': List of servers (separated by commas) to which send the informations
*'''Servers''': List of servers (separated by commas) to which send the informations
*'''TCPPort''': TCP port on which the proxy listen. Clients will connect on the proxy as if it's a zabbix server. The default is 10051
*'''TCPPort''': TCP port on which the proxy listen. Clients will connect on the proxy as if it's a Zabbix server. The default is 10051
*'''access''': (private|public) If you want to open zabbix-proxy on the external interface. If you set this to public, you should use the AllowHosts key to limit the access
*'''access''': (private|public) If you want to open zabbix-proxy on the external interface. If you set this to public, you should use the AllowHosts key to limit the access
*'''status''': (enabled|disabled) Should the service be starte dautomatically
*'''status''': (enabled|disabled) Should the service be started automatically
=== Monitoring SME servers ===
=== Monitoring SME servers ===
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)
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:
It'll create some new templates in zabbix:
*Template_SME is for agents running in active mode (default of the contrib)
*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)
*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 (usefull if you use [[CoovaChilli]] contrib)
*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.
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.
Templates '''Template_SME''' and '''Template_SME_dynip''' are based on other templates you can use for other hosts (non SME):
Templates '''Template_SME''' and '''Template_SME_dynip''' 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_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.
*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_app_MySQL: reports MySQL statistics
