5 Simple checks

Overview

Simple checks are normally used for remote agent-less checks of services.

Note that Zabbix agent is not needed for simple checks. Zabbix server/proxy is responsible for the processing of simple checks (making external connections, etc).

Examples of using simple checks:

net.tcp.service[ftp,,155]
       net.tcp.service[http]
       net.tcp.service.perf[http,,8080]
       net.udp.service.perf[ntp]

Supported checks

The item keys are listed without optional parameters and additional information. Click on the item key to see the full details.

See also VMware monitoring item keys.

Item key details

icmpping[<target>,<packets>,<interval>,<size>,<timeout>]

The host accessibility by ICMP ping.
Return value: 0 - ICMP ping fails; 1 - ICMP ping successful.

Parameters:

• target - the host IP or DNS name;
• packets - the number of packets;
• interval - the time between successive packets in milliseconds;
• size - the packet size in bytes;
• timeout - the timeout in milliseconds.

See also the table of default values.

Example:

icmpping[,4] #If at least one packet of the four is returned, the item will return 1.

icmppingloss[<target>,<packets>,<interval>,<size>,<timeout>]

The percentage of lost packets.
Return value: Float.

Parameters:

• target - the host IP or DNS name;
• packets - the number of packets;
• interval - the time between successive packets in milliseconds;
• size - the packet size in bytes;
• timeout - the timeout in milliseconds.

See also the table of default values.

icmppingsec[<target>,<packets>,<interval>,<size>,<timeout>,<mode>]

The ICMP ping response time (in seconds).
Return value: Float.

Parameters:

• target - the host IP or DNS name;
• packets - the number of packets;
• interval - the time between successive packets in milliseconds;
• size - the packet size in bytes;
• timeout - the timeout in milliseconds;
• mode - possible values: min, max, or avg (default).

Comments:

• Packets which are lost or timed out are not used in the calculation;
• If the host is not available (timeout reached), the item will return 0;
• If the return value is less than 0.0001 seconds, the value will be set to 0.0001 seconds;
• See also the table of default values.

net.tcp.service[service,<ip>,<port>]

Checks if a service is running and accepting TCP connections.
Return value: 0 - the service is down; 1 - the service is running.

Parameters:

• service - possible values: ssh, ldap, smtp, ftp, http, pop, nntp, imap, tcp, https, telnet (see details);
• ip - the IP address or DNS name (by default the host IP/DNS is used);
• port - the port number (by default the standard service port number is used).

Comments:

• Note that with tcp service indicating the port is mandatory;
• These checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually);
• Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.service[tcp,<ip>,port] for checks like these.

Example:

net.tcp.service[ftp,,45] #This item can be used to test the availability of FTP server on TCP port 45.

net.tcp.service.perf[service,<ip>,<port>]

Checks the performance of a TCP service.
Return value: Float: 0.000000 - the service is down; seconds - the number of seconds spent while connecting to the service.

Parameters:

• service - possible values: ssh, ldap, smtp, ftp, http, pop, nntp, imap, tcp, https, telnet (see details);
• ip - the IP address or DNS name (by default the host IP/DNS is used);
• port - the port number (by default the standard service port number is used).

Comments:

• Note that with tcp service indicating the port is mandatory;
• Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.service[tcp,<ip>,port] for checks like these.

Example:

net.tcp.service.perf[ssh] #This item can be used to test the speed of initial response from SSH server.

net.udp.service[service,<ip>,<port>]

Checks if a service is running and responding to UDP requests.
Return value: 0 - the service is down; 1 - the service is running.

Parameters:

• service - possible values: ntp (see details);
• ip - the IP address or DNS name (by default the host IP/DNS is used);
• port - the port number (by default the standard service port number is used).

Example:

net.udp.service[ntp,,45] #This item can be used to test the availability of NTP service on UDP port 45.

net.udp.service.perf[service,<ip>,<port>]

Checks the performance of a UDP service.
Return value: Float: 0.000000 - the service is down; seconds - the number of seconds spent waiting for response from the service.

Parameters:

• service - possible values: ntp (see details);
• ip - the IP address or DNS name (by default the host IP/DNS is used);
• port - the port number (by default the standard service port number is used).

Example:

net.udp.service.perf[ntp] #This item can be used to test the response time from NTP service.

Timeout processing

Zabbix will not process a simple check longer than the Timeout seconds defined in the Zabbix server/proxy configuration file.

ICMP pings

Zabbix uses an external utility fping to process ICMP pings (icmpping, icmppingloss, icmppingsec).

Installation

fping is not included with Zabbix and needs to be installed separately:

• Various Unix-based platforms have the fping package in their default repositories, but it is not pre-installed. In this case you can use the package manager to install fping.

• Zabbix provides fping packages for RHEL. Please note that these packages are provided without official support.

• fping can also be compiled from source.

Configuration

Specify fping location in the FpingLocation parameter of Zabbix server/proxy configuration file (or Fping6Location parameter for using IPv6 addresses).

fping should be executable by the user Zabbix server/proxy run as and this user should have sufficient rights.

See also: Known issues for processing simple checks with fping versions below 3.10.

Default values

Defaults, limits and description of values for ICMP check parameters:

The defaults may differ slightly depending on the platform and version.

In addition, Zabbix uses fping options -i interval ms (do not mix up with the item parameter interval mentioned in the table above, which corresponds to fping option -p) and -S source IP address (or -I in older fping versions). These options are auto-detected by running checks with different option combinations. Zabbix tries to detect the minimal value in milliseconds that fping allows to use with -i by trying 3 values: 0, 1 and 10. The value that first succeeds is then used for subsequent ICMP checks. This process is done by each ICMP pinger process individually.

Auto-detected fping options are invalidated every hour and detected again on the next attempt to perform ICMP check. Set DebugLevel>=4 in order to view details of this process in the server or proxy log file.

Zabbix writes IP addresses to be checked by any of the three icmpping* keys to a temporary file, which is then passed to fping. If items have different key parameters, only the ones with identical key parameters are written to a single file. All IP addresses written to the single file will be checked by fping in parallel, so Zabbix ICMP pinger process will spend fixed amount of time disregarding the number of IP addresses in the file.