Timeout after which agent is considered unavailable. Works only for agents reachable from Zabbix server/proxy (passive mode).

Critical threshold of CPU utilization expressed in %.

The CPU load per core is considered sustainable. If necessary, it can be tuned.

Used for filesystem discovery. Can be overridden on the host or linked template level.

Used for filesystem discovery. Can be overridden on the host or linked template level.

Used for filesystem discovery. Can be overridden on the host or linked template level.

Used for filesystem discovery. Can be overridden on the host or linked template level.

The critical threshold of the filesystem metadata utilization.

The warning threshold of the filesystem metadata utilization.

The critical threshold of the filesystem utilization.

The warning threshold of the filesystem utilization.

Used as a threshold in the memory utilization trigger.

Used as a threshold in the available memory trigger.

The warning threshold of the minimum free swap.

The average response time (in ms) of disk read before the trigger fires.

The average response time (in ms) of disk write before the trigger fires.

Used for block device discovery. Can be overridden on the host or linked template level.

Used for block device discovery. Can be overridden on the host or linked template level.

Warning threshold of error packet rate. Can be used with interface name as context.

Link status trigger will be fired only for interfaces where the context macro equals "1".

Used for network interface discovery. Can be overridden on the host or linked template level.

Filters out loopbacks, nulls, docker veth links and docker0 bridge by default.

Used as a threshold in the interface utilization trigger.

The upper threshold for difference of system time.

The lower threshold for difference of system time. Used in recovery expression to avoid trigger flapping.

Preprocessing

• Discard unchanged with heartbeat: 1d

Preprocessing

• Discard unchanged with heartbeat: 1d

The agent always returns 1 for this item. It could be used in combination with nodata() for availability check.

Monitoring the availability status of the agent.

Preprocessing

• Discard unchanged with heartbeat: 1d

Calculated as the system CPU load divided by the number of CPU cores.

Calculated as the system CPU load divided by the number of CPU cores.

Calculated as the system CPU load divided by the number of CPU cores.

CPU utilization expressed in %.

Preprocessing

• JavaScript: //Calculate utilization<br>return (100 - value)

Time the CPU has spent doing nothing.

Time the CPU has spent running the kernel and its processes.

Time the CPU has spent running users' processes that are not niced.

Time the CPU has spent running users' processes that have been niced.

Time the CPU has been waiting for I/O to complete.

The amount of "stolen" CPU from this virtual machine by the hypervisor for other tasks, such as running another virtual machine.

Time the CPU has spent servicing hardware interrupts.

Time the CPU has been servicing software interrupts.

Time spent on running a virtual CPU for a guest operating system.

Time spent on running a niced guest (a virtual CPU for guest operating systems under the control of the Linux kernel).

The combined rate at which all processors on the computer are switched from one thread to another.

Preprocessing

• Change per second

Number of interrupts processed.

Preprocessing

• Change per second

The vfs.fs.get key acquires raw information set about the filesystems. Later to be extracted by preprocessing in dependent items.

The percentage of used memory is calculated as 100-pavailable.

Preprocessing

• JavaScript: return (100-value);

The available memory as percentage of the total. See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item.

Total memory expressed in bytes.

The available memory:

- in Linux = free + buffers + cache;

- on other platforms calculation may vary.

See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item.

The total space of the swap volume/file expressed in bytes.

The free space of the swap volume/file expressed in bytes.

The free space of the swap volume/file expressed in %.

The system uptime expressed in the following format: "N days, hh:mm:ss".

Preprocessing

• Discard unchanged with heartbeat: 1h

The local system time of the host.

The host name of the system.

Preprocessing

• Discard unchanged with heartbeat: 12h

The information as normally returned by uname -a.

Preprocessing

• Discard unchanged with heartbeat: 12h

The number of users who are currently logged in.

May be increased by using the sysctl utility or modifying the file /etc/sysctl.conf.

Preprocessing

• Discard unchanged with heartbeat: 1d

May be increased by using the sysctl utility or modifying the file /etc/sysctl.conf.

Preprocessing

• Discard unchanged with heartbeat: 1d

Preprocessing

• Discard unchanged with heartbeat: 1h

Preprocessing

• Discard unchanged with heartbeat: 1d

The architecture of the operating system.

Preprocessing

• Discard unchanged with heartbeat: 1d

Preprocessing

• JSON Path: $.length()

• Discard unchanged with heartbeat: 12h

For passive only agents, host availability is used with {$AGENT.TIMEOUT} as time threshold.

The load average per CPU is too high. The system may be slow to respond.

CPU utilization is too high. The system might be slow to respond.

• Linux: Load average is too high

The system is running out of free memory.

• Linux: Lack of available memory

The system is running out of memory.

If there is no swap configured, this trigger is ignored.

• Linux: Lack of available memory
• Linux: High memory utilization

The host uptime is less than 10 minutes.

The host's system time is different from Zabbix server time.

The name of the system has changed. Acknowledge to close the problem manually.

• Linux: Getting closer to process limit

• Linux: System name has changed
• Linux: Operating system description has changed

The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.

• Linux: System name has changed

The discovery of mounted filesystems with different types.

Preprocessing

• JavaScript: The text is too long. Please see the template.

• Discard unchanged with heartbeat: 1h

Intermediate data of {#FSNAME} filesystem.

Preprocessing

• JSON Path: $.[?(@.fsname=='{#FSNAME}')].first()

The filesystem is mounted as read-only. It is available only for Zabbix agents 6.4 and higher.

Preprocessing

• JSON Path: $.options

  ⛔️Custom on fail: Discard value

• Regular expression: `(?:^

Used storage expressed in bytes.

Preprocessing

• JSON Path: $.bytes.used

Total space expressed in bytes.

Preprocessing

• JSON Path: $.bytes.total

Calculated as the percentage of currently used space compared to the maximum available space.

Preprocessing

• JSON Path: $.bytes.pused

Available storage space expressed in bytes.

Preprocessing

• JSON Path: $.bytes.free

Free metadata space expressed in %.

Preprocessing

• JSON Path: $.inodes.pfree

The filesystem has become read-only, possibly due to an I/O error. Available only for Zabbix agents 6.4 and higher.

The volume's space usage exceeds the {$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"}% limit.
The trigger expression is based on the current used and maximum available spaces.
Event name represents the total volume space, which can differ from the maximum available space, depending on the filesystem type.

The volume's space usage exceeds the {$VFS.FS.PUSED.MAX.WARN:"{#FSNAME}"}% limit.
The trigger expression is based on the current used and maximum available spaces.
Event name represents the total volume space, which can differ from the maximum available space, depending on the filesystem type.

• FS [{#FSNAME}]: Space is critically low

Disk writing may fail if index nodes are exhausted, leading to error messages like "No space left on device" or "Disk is full", despite available free space.

Disk writing may fail if index nodes are exhausted, leading to error messages like "No space left on device" or "Disk is full", despite available free space.

• FS [{#FSNAME}]: Running out of free inodes

Preprocessing

• Discard unchanged with heartbeat: 1h

The contents of get /sys/block/{#DEVNAME}/stat to get the disk statistics.

Preprocessing

• JavaScript: return JSON.stringify(value.trim().split(/ +/));

r/s (read operations per second) - the number (after merges) of read requests completed per second for the device.

Preprocessing

• JSON Path: $[0]

• Change per second

w/s (write operations per second) - the number (after merges) of write requests completed per second for the device.

Preprocessing

• JSON Path: $[4]

• Change per second

The rate of total read time counter; used in r_await calculation.

Preprocessing

• JSON Path: $[3]

• Change per second

• Custom multiplier: 0.001

The rate of total write time counter; used in w_await calculation.

Preprocessing

• JSON Path: $[7]

• Change per second

• Custom multiplier: 0.001

This formula contains two Boolean expressions that evaluate to 1 or 0 in order to set the calculated metric to zero and to avoid the exception - division by zero.

This formula contains two Boolean expressions that evaluate to 1 or 0 in order to set the calculated metric to zero and to avoid the exception - division by zero.

The current average disk queue; the number of requests outstanding on the disk while the performance data is being collected.

Preprocessing

• JSON Path: $[10]

• Change per second

• Custom multiplier: 0.001

The percentage of elapsed time during which the selected disk drive was busy while servicing read or write requests.

Preprocessing

• JSON Path: $[9]

• Change per second

• Custom multiplier: 0.1

This trigger might indicate the disk {#DEVNAME} saturation.

The discovery of network interfaces.

Preprocessing

• Change per second

• Custom multiplier: 8

Preprocessing

• Change per second

• Custom multiplier: 8

Preprocessing

• Change per second

Preprocessing

• Change per second

Preprocessing

• Change per second

Preprocessing

• Change per second

Reference: https://www.kernel.org/doc/Documentation/networking/operstates.txt

Preprocessing

• JavaScript: The text is too long. Please see the template.

It indicates the interface protocol type as a decimal value.

See include/uapi/linux/if_arp.h for all possible values.

Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net

Preprocessing

• Discard unchanged with heartbeat: 1d

It indicates the latest or current speed value of the interface. The value is an integer representing the link speed expressed in bits/sec.

This attribute is only valid for the interfaces that implement the ethtool get_link_ksettings method (mostly Ethernet).

Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net

Preprocessing

• Custom multiplier: 1000000

• Discard unchanged with heartbeat: 1h

The utilization of the network interface is close to its estimated maximum bandwidth.

• Interface {#IFNAME}: Link down

It recovers when it is below 80% of the {$IF.ERRORS.WARN:"{#IFNAME}"} threshold.

• Interface {#IFNAME}: Link down

This trigger expression works as follows:
1. It can be triggered if the operations status is down.
2. {$IFCONTROL:"{#IFNAME}"}=1 - a user can redefine the context macro to "0", marking this interface as not important. No new trigger will be fired if this interface is down.
3. last(/TEMPLATE_NAME/METRIC,#1)<>last(/TEMPLATE_NAME/METRIC,#2) - the trigger fires only if the operational status was up to (1) sometime before (so, does not fire for "eternal off" interfaces.)

WARNING: if closed manually - it will not fire again on the next poll, because of .diff.

This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Acknowledge to close the problem manually.

• Interface {#IFNAME}: Link down

Timeout after which agent is considered unavailable. Works only for agents reachable from Zabbix server/proxy (passive mode).

-

-

This macro is used as a threshold in the interface utilization trigger.

-

-

-

CPU load per core is considered sustainable. If necessary, it can be tuned.

This macro is used as a threshold in the memory available trigger.

This macro is used as a threshold in the memory utilization trigger.

-

It filters out loopbacks, nulls, docker veth links and docker0 bridge by default.

-

-

This macro is used for a discovery of block devices. It can be overridden on host level or its linked template level.

This macro is used for a discovery of block devices. It can be overridden on host level or its linked template level.

The average response time (in ms) of disk read before the trigger would fire.

The average response time (in ms) of disk write before the trigger would fire.

The critical threshold for utilization of the filesystem.

The warning threshold for utilization of the filesystem.

This macro is used for discovery of the filesystems. It can be overridden on host level or its linked template level.

This macro is used for discovery of the filesystems. It can be overridden on host level or its linked template level.

This macro is used for discovery of the filesystems. It can be overridden on host level or its linked template level.

This macro is used for discovery of the filesystems. It can be overridden on host level or its linked template level.

-

-

-

-

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

Filter:

- {#DEVTYPE} MATCHES_REGEX disk

- {#DEVNAME} MATCHES_REGEX {$VFS.DEV.DEVNAME.MATCHES}

- {#DEVNAME} NOT_MATCHES_REGEX {$VFS.DEV.DEVNAME.NOT_MATCHES}

The discovery of mounted filesystems with different types.

Filter:

- {#FSTYPE} MATCHES_REGEX {$VFS.FS.FSTYPE.MATCHES}

- {#FSTYPE} NOT_MATCHES_REGEX {$VFS.FS.FSTYPE.NOT_MATCHES}

- {#FSNAME} MATCHES_REGEX {$VFS.FS.FSNAME.MATCHES}

- {#FSNAME} NOT_MATCHES_REGEX {$VFS.FS.FSNAME.NOT_MATCHES}

Overrides:

Skip metadata collection for dynamic FS
- {#FSTYPE} MATCHES_REGEX `^(btrfs

The discovery of network interfaces.

Filter:

- {#IFNAME} MATCHES_REGEX {$NET.IF.IFNAME.MATCHES}

- {#IFNAME} NOT_MATCHES_REGEX {$NET.IF.IFNAME.NOT_MATCHES}

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

-

-

The CPU utilization expressed in %.

Preprocessing:

- JAVASCRIPT: //Calculate utilization return (100 - value)

The time the CPU has spent doing nothing.

The time the CPU has spent running the kernel and its processes.

The time the CPU has spent running users' processes that are not niced.

The time the CPU has spent running users' processes that have been niced.

The amount of time the CPU has been waiting for I/O to complete.

The amount of 'stolen' CPU from this virtual machine by the hypervisor for other tasks, such as running another virtual machine.

The amount of time the CPU has been servicing hardware interrupts.

The amount of time the CPU has been servicing software interrupts.

Guest time - the time spent on running a virtual CPU for a guest operating system.

The time spent on running a niced guest (a virtual CPU for guest operating systems under the control of the Linux kernel).

-

Preprocessing:

- CHANGE_PER_SECOND

-

Preprocessing:

- CHANGE_PER_SECOND

Used storage expressed in Bytes

The total space expressed in Bytes.

The space utilization expressed in % for {#FSNAME}.

-

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

The local system time of the host.

The host name of the system.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 12h

The information as normally returned by 'uname -a'.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 12h

The number of users who are currently logged in.

It could be increased by using sysctl utility or modifying the file /etc/sysctl.conf.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

It could be increased by using sysctl utility or modifying the file /etc/sysctl.conf.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

-

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

The architecture of the host's operating system.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

The percentage of used memory is calculated as 100-pavailable.

Preprocessing:

- JAVASCRIPT: return (100-value);

The available memory as percentage of the total. See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item.

The total memory expressed in Bytes.

The available memory:

- in Linux - available = free + buffers + cache;

- on other platforms calculation may vary.

See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item.

The total space of the swap volume/file expressed in bytes.

The free space of the swap volume/file expressed in bytes.

The free space of the swap volume/file expressed in %.

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

The agent always returns 1 for this item. It could be used in combination with nodata() for availability check.

-

Preprocessing:

- CHANGE_PER_SECOND

- MULTIPLIER: 8

-

Preprocessing:

- CHANGE_PER_SECOND

- MULTIPLIER: 8

-

Preprocessing:

- CHANGE_PER_SECOND

-

Preprocessing:

- CHANGE_PER_SECOND

-

Preprocessing:

- CHANGE_PER_SECOND

-

Preprocessing:

- CHANGE_PER_SECOND

Reference: https://www.kernel.org/doc/Documentation/networking/operstates.txt

Preprocessing:

- JAVASCRIPT: The text is too long. Please see the template.

It indicates the interface protocol type as a decimal value.

See include/uapi/linux/if_arp.h for all possible values.

Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

It indicates the latest or current speed value of the interface. The value is an integer representing the link speed expressed in bits/sec.

This attribute is only valid for the interfaces that implement the ethtool get_link_ksettings method (mostly Ethernet).

Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net

Preprocessing:

- MULTIPLIER: 1000000

- DISCARD_UNCHANGED_HEARTBEAT: 1h

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

The system uptime expressed in the following format:'N days, hh:mm:ss'.

Monitoring the availability status of the agent.

r/s (read operations per second) - the number (after merges) of read requests completed per second for the device.

Preprocessing:

- JSONPATH: $[0]

- CHANGE_PER_SECOND

w/s (write operations per second) - the number (after merges) of write requests completed per second for the device.

Preprocessing:

- JSONPATH: $[4]

- CHANGE_PER_SECOND

This formula contains two boolean expressions that evaluate to 1 or 0 in order to set the calculated metric to zero and to avoid the exception - division by zero.

Expression:

This formula contains two boolean expressions that evaluate to 1 or 0 in order to set the calculated metric to zero and to avoid the exception - division by zero.

Expression:

The current average disk queue; the number of requests outstanding on the disk while the performance data is being collected.

Preprocessing:

- JSONPATH: $[10]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.001

This item is the percentage of elapsed time during which the selected disk drive was busy while servicing read or write requests.

Preprocessing:

- JSONPATH: $[9]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.1

The contents of get /sys/block/{#DEVNAME}/stat to get the disk statistics.

Preprocessing:

- JAVASCRIPT: return JSON.stringify(value.trim().split(/ +/));

The rate of total read time counter; used in r_await calculation.

Preprocessing:

- JSONPATH: $[3]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.001

The rate of total write time counter; used in w_await calculation.

Preprocessing:

- JSONPATH: $[7]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.001

The load average per CPU is too high. The system may be slow to respond.

The CPU utilization is too high. The system might be slow to respond.

Depends on:

- Load average is too high

Two conditions should match:

1. The first condition - utilization of space should be above {$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"}.

2. The second condition should be one of the following:

- the disk free space is less than {$VFS.FS.FREE.MIN.CRIT:"{#FSNAME}"};

- the disk will be full in less than 24 hours.

Manual close: YES

Two conditions should match:

1. The first condition - utilization of space should be above {$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"}.

2. The second condition should be one of the following:

- the disk free space is less than {$VFS.FS.FREE.MIN.WARN:"{#FSNAME}"};

- the disk will be full in less than 24 hours.

Manual close: YES

Depends on:

- {#FSNAME}: Disk space is critically low

It may become impossible to write to a disk if there are no index nodes left.

Following error messages may be returned as symptoms, even though the free space is available:

- 'No space left on device';

- 'Disk is full'.

It may become impossible to write to a disk if there are no index nodes left.

Following error messages may be returned as symptoms, even though the free space is available:

- 'No space left on device';

- 'Disk is full'.

Depends on:

- {#FSNAME}: Running out of free inodes

The host's system time is different from Zabbix server time.

Manual close: YES

The name of the system has changed. Ack to close the problem manually.

Manual close: YES

-

-

Depends on:

- Getting closer to process limit

-

The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Ack to close the problem manually.

Manual close: YES

Depends on:

- System name has changed

The system is running out of free memory.

Depends on:

- Lack of available memory

-

If there is no swap configured, this trigger is ignored.

Depends on:

- High memory utilization

- Lack of available memory

The utilization of the network interface is close to its estimated maximum bandwidth.

Recovery expression:

Manual close: YES

Depends on:

- Interface {#IFNAME}: Link down

It recovers when it is below 80% of the {$IF.ERRORS.WARN:"{#IFNAME}"} threshold

Recovery expression:

Manual close: YES

Depends on:

- Interface {#IFNAME}: Link down

This trigger expression works as follows:

1. It can be triggered if the operations status is down.

2. {$IFCONTROL:"{#IFNAME}"}=1 - a user can redefine context macro to value - 0. That marks this interface as not important. No new trigger will be fired if this interface is down.

3. {TEMPLATE_NAME:METRIC.diff()}=1) - the trigger fires only if the operational status was up to (1) sometime before (so, do not fire for the 'ethernal off' interfaces.)

WARNING: if closed manually - it will not fire again on the next poll, because of .diff.

Recovery expression:

Manual close: YES

This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Acknowledge (Ack) to close the problem manually.

Recovery expression:

Manual close: YES

Depends on:

- Interface {#IFNAME}: Link down

-

Manual close: YES

Depends on:

- Operating system description has changed

- System name has changed

The host uptime is less than 10 minutes

Manual close: YES

For passive only agents, host availability is used with {$AGENT.TIMEOUT} as time threshold.

Manual close: YES

This trigger might indicate the disk {#DEVNAME} saturation.

Manual close: YES

Timeout after which agent is considered unavailable. Works only for agents reachable from Zabbix server/proxy (passive mode).

The CPU load per core is considered sustainable. If necessary, it can be tuned.

This macro is used for discovery of the filesystems. It can be overridden on host level or its linked template level.

This macro is used for discovery of the filesystems. It can be overridden on host level or its linked template level.

This macro is used for discovery of the filesystems. It can be overridden on host level or its linked template level.

This macro is used for discovery of the filesystems. It can be overridden on host level or its linked template level.

The critical threshold of the filesystem metadata utilization.

The warning threshold of the filesystem metadata utilization.

The critical threshold of the filesystem utilization.

The warning threshold of the filesystem utilization.

This macro is used as a threshold in the memory utilization trigger.

This macro is used as a threshold in the memory available trigger.

The average response time (in ms) of disk read before the trigger would fire.

The average response time (in ms) of disk write before the trigger would fire.

This macro is used for a discovery of block devices. It can be overridden on host level or its linked template level.

This macro is used for a discovery of block devices. It can be overridden on host level or its linked template level.

It filters out loopbacks, nulls, docker veth links and docker0 bridge by default.

This macro is used as a threshold in the interface utilization trigger.

The upper threshold for difference of system time.

The lower threshold for difference of system time. Used in recovery expression to avoid trigger flapping.

Preprocessing

• Discard unchanged with heartbeat: 1d

Preprocessing

• Discard unchanged with heartbeat: 1d

The agent always returns 1 for this item. It could be used in combination with nodata() for availability check.

Monitoring the availability status of the agent.

Preprocessing

• Discard unchanged with heartbeat: 1d

The CPU utilization expressed in %.

Preprocessing

• JavaScript: //Calculate utilization<br>return (100 - value)

The time the CPU has spent doing nothing.

The time the CPU has spent running the kernel and its processes.

The time the CPU has spent running users' processes that are not niced.

The time the CPU has spent running users' processes that have been niced.

The amount of time the CPU has been waiting for I/O to complete.

The amount of "stolen" CPU from this virtual machine by the hypervisor for other tasks, such as running another virtual machine.

The amount of time the CPU has been servicing hardware interrupts.

The amount of time the CPU has been servicing software interrupts.

Guest time - the time spent on running a virtual CPU for a guest operating system.

The time spent on running a niced guest (a virtual CPU for guest operating systems under the control of the Linux kernel).

Preprocessing

• Change per second

Preprocessing

• Change per second

The percentage of used memory is calculated as 100-pavailable.

Preprocessing

• JavaScript: return (100-value);

The available memory as percentage of the total. See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item.

The total memory expressed in bytes.

The available memory:

- in Linux - available = free + buffers + cache;

- on other platforms calculation may vary.

See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item.

The total space of the swap volume/file expressed in bytes.

The free space of the swap volume/file expressed in bytes.

The free space of the swap volume/file expressed in %.

The system uptime expressed in the following format: "N days, hh:mm:ss".

Preprocessing

• Discard unchanged with heartbeat: 1h

The local system time of the host.

The host name of the system.

Preprocessing

• Discard unchanged with heartbeat: 12h

The information as normally returned by uname -a.

Preprocessing

• Discard unchanged with heartbeat: 12h

The number of users who are currently logged in.

It could be increased by using sysctl utility or modifying the file /etc/sysctl.conf.

Preprocessing

• Discard unchanged with heartbeat: 1d

It could be increased by using sysctl utility or modifying the file /etc/sysctl.conf.

Preprocessing

• Discard unchanged with heartbeat: 1d

Preprocessing

• Discard unchanged with heartbeat: 1h

Preprocessing

• Discard unchanged with heartbeat: 1d

The architecture of the operating system.

Preprocessing

• Discard unchanged with heartbeat: 1d

Preprocessing

• Discard unchanged with heartbeat: 1d

For passive only agents, host availability is used with {$AGENT.TIMEOUT} as time threshold.

The load average per CPU is too high. The system may be slow to respond.

The CPU utilization is too high. The system might be slow to respond.

• Linux: Load average is too high

The system is running out of free memory.

• Linux: Lack of available memory

If there is no swap configured, this trigger is ignored.

• Linux: Lack of available memory
• Linux: High memory utilization

The host uptime is less than 10 minutes.

The host's system time is different from Zabbix server time.

The name of the system has changed. Acknowledge to close the problem manually.

• Linux: Getting closer to process limit

• Linux: System name has changed
• Linux: Operating system description has changed

The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.

• Linux: System name has changed

The discovery of mounted filesystems with different types.

Used storage in bytes

Total space in bytes

The space utilization expressed in % for {#FSNAME}.

The volume's space usage exceeds the {$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"} limit.

The volume's space usage exceeds the {$VFS.FS.PUSED.MAX.WARN:"{#FSNAME}"} limit.

• {#FSNAME}: Disk space is critically low

It may become impossible to write to a disk if there are no index nodes left.
The following error messages may be returned as symptoms, even though the free space is available:
- 'No space left on device';
- 'Disk is full'.

It may become impossible to write to a disk if there are no index nodes left.
The following error messages may be returned as symptoms, even though the free space is available:
- 'No space left on device';
- 'Disk is full'.

• {#FSNAME}: Running out of free inodes

Preprocessing

• Discard unchanged with heartbeat: 1h

The contents of get /sys/block/{#DEVNAME}/stat to get the disk statistics.

Preprocessing

• JavaScript: return JSON.stringify(value.trim().split(/ +/));

r/s (read operations per second) - the number (after merges) of read requests completed per second for the device.

Preprocessing

• JSON Path: $[0]

• Change per second

w/s (write operations per second) - the number (after merges) of write requests completed per second for the device.

Preprocessing

• JSON Path: $[4]

• Change per second

The rate of total read time counter; used in r_await calculation.

Preprocessing

• JSON Path: $[3]

• Change per second

• Custom multiplier: 0.001

The rate of total write time counter; used in w_await calculation.

Preprocessing

• JSON Path: $[7]

• Change per second

• Custom multiplier: 0.001

This formula contains two Boolean expressions that evaluate to 1 or 0 in order to set the calculated metric to zero and to avoid the exception - division by zero.

This formula contains two Boolean expressions that evaluate to 1 or 0 in order to set the calculated metric to zero and to avoid the exception - division by zero.

The current average disk queue; the number of requests outstanding on the disk while the performance data is being collected.

Preprocessing

• JSON Path: $[10]

• Change per second

• Custom multiplier: 0.001

This item is the percentage of elapsed time during which the selected disk drive was busy while servicing read or write requests.

Preprocessing

• JSON Path: $[9]

• Change per second

• Custom multiplier: 0.1

This trigger might indicate the disk {#DEVNAME} saturation.

The discovery of network interfaces.

Preprocessing

• Change per second

• Custom multiplier: 8

Preprocessing

• Change per second

• Custom multiplier: 8

Preprocessing

• Change per second

Preprocessing

• Change per second

Preprocessing

• Change per second

Preprocessing

• Change per second

Reference: https://www.kernel.org/doc/Documentation/networking/operstates.txt

Preprocessing

• JavaScript: The text is too long. Please see the template.

It indicates the interface protocol type as a decimal value.

See include/uapi/linux/if_arp.h for all possible values.

Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net

Preprocessing

• Discard unchanged with heartbeat: 1d

It indicates the latest or current speed value of the interface. The value is an integer representing the link speed expressed in bits/sec.

This attribute is only valid for the interfaces that implement the ethtool get_link_ksettings method (mostly Ethernet).

Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net

Preprocessing

• Custom multiplier: 1000000

• Discard unchanged with heartbeat: 1h

The utilization of the network interface is close to its estimated maximum bandwidth.

• Interface {#IFNAME}: Link down

It recovers when it is below 80% of the {$IF.ERRORS.WARN:"{#IFNAME}"} threshold.

• Interface {#IFNAME}: Link down

This trigger expression works as follows:
1. It can be triggered if the operations status is down.
2. {$IFCONTROL:"{#IFNAME}"}=1 - a user can redefine context macro to value - 0. That marks this interface as not important. No new trigger will be fired if this interface is down.
3. {TEMPLATE_NAME:METRIC.diff()}=1 - the trigger fires only if the operational status was up to (1) sometime before (so, do not fire for the 'eternal off' interfaces.)

WARNING: if closed manually - it will not fire again on the next poll, because of .diff.

This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Acknowledge to close the problem manually.

• Interface {#IFNAME}: Link down

-

Load per CPU considered sustainable. Tune if needed.

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

-

-

CPU utilization in %

Preprocessing:

- JAVASCRIPT: //Calculate utilization return (100 - value)

The time the CPU has spent doing nothing.

The time the CPU has spent running the kernel and its processes.

The time the CPU has spent running users' processes that are not niced.

The time the CPU has spent running users' processes that have been niced.

Amount of time the CPU has been waiting for I/O to complete.

The amount of CPU 'stolen' from this virtual machine by the hypervisor for other tasks (such as running another virtual machine).

The amount of time the CPU has been servicing hardware interrupts.

The amount of time the CPU has been servicing software interrupts.

Guest time (time spent running a virtual CPU for a guest operating system)

Time spent running a niced guest (virtual CPU for guest operating systems under the control of the Linux kernel)

-

Preprocessing:

- CHANGE_PER_SECOND

-

Preprocessing:

- CHANGE_PER_SECOND

Per CPU load average is too high. Your system may be slow to respond.

CPU utilization is too high. The system might be slow to respond.

Depends on:

- Load average is too high (per CPU load over {$LOAD_AVG_PER_CPU.MAX.WARN} for 5m)

This macro is used in filesystems discovery. Can be overridden on the host or linked template level

This macro is used in filesystems discovery. Can be overridden on the host or linked template level

This macro is used in filesystems discovery. Can be overridden on the host or linked template level

This macro is used in filesystems discovery. Can be overridden on the host or linked template level

-

-

-

-

Discovery of file systems of different types.

Filter:

- {#FSTYPE} MATCHES_REGEX {$VFS.FS.FSTYPE.MATCHES}

- {#FSTYPE} NOT_MATCHES_REGEX {$VFS.FS.FSTYPE.NOT_MATCHES}

- {#FSNAME} MATCHES_REGEX {$VFS.FS.FSNAME.MATCHES}

- {#FSNAME} NOT_MATCHES_REGEX {$VFS.FS.FSNAME.NOT_MATCHES}

Used storage in Bytes

Total space in Bytes

Space utilization in % for {#FSNAME}

-

Two conditions should match: First, space utilization should be above {$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"}.

Second condition should be one of the following:

- The disk free space is less than 5G.

- The disk will be full in less than 24 hours.

Manual close: YES

Two conditions should match: First, space utilization should be above {$VFS.FS.PUSED.MAX.WARN:"{#FSNAME}"}.

Second condition should be one of the following:

- The disk free space is less than 10G.

- The disk will be full in less than 24 hours.

Manual close: YES

Depends on:

- {#FSNAME}: Disk space is critically low (used > {$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"}%)

It may become impossible to write to disk if there are no index nodes left.

As symptoms, 'No space left on device' or 'Disk is full' errors may be seen even though free space is available.

It may become impossible to write to disk if there are no index nodes left.

As symptoms, 'No space left on device' or 'Disk is full' errors may be seen even though free space is available.

Depends on:

- {#FSNAME}: Running out of free inodes (free < {$VFS.FS.INODE.PFREE.MIN.CRIT:"{#FSNAME}"}%)

This macro is used as a threshold in memory available trigger.

This macro is used as a threshold in memory utilization trigger.

-

Memory used percentage is calculated as (100-pavailable)

Preprocessing:

- JAVASCRIPT: return (100-value);

Available memory as percentage of total. See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item.

Total memory in Bytes

Available memory, in Linux, available = free + buffers + cache. On other platforms calculation may vary. See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item.

The total space of swap volume/file in bytes.

The free space of swap volume/file in bytes.

The free space of swap volume/file in percent.

The system is running out of free memory.

Depends on:

- Lack of available memory (<{$MEMORY.AVAILABLE.MIN} of {ITEM.VALUE2})

-

This trigger is ignored, if there is no swap configured

Depends on:

- High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)

- Lack of available memory (<{$MEMORY.AVAILABLE.MIN} of {ITEM.VALUE2})

This macro is used in block devices discovery. Can be overridden on the host or linked template level

This macro is used in block devices discovery. Can be overridden on the host or linked template level

Disk read average response time (in ms) before the trigger would fire

Disk write average response time (in ms) before the trigger would fire

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

Filter:

- {#DEVTYPE} MATCHES_REGEX disk

- {#DEVNAME} MATCHES_REGEX {$VFS.DEV.DEVNAME.MATCHES}

- {#DEVNAME} NOT_MATCHES_REGEX {$VFS.DEV.DEVNAME.NOT_MATCHES}

r/s. The number (after merges) of read requests completed per second for the device.

Preprocessing:

- JSONPATH: $[0]

- CHANGE_PER_SECOND

w/s. The number (after merges) of write requests completed per second for the device.

Preprocessing:

- JSONPATH: $[4]

- CHANGE_PER_SECOND

This formula contains two boolean expressions that evaluates to 1 or 0 in order to set calculated metric to zero and to avoid division by zero exception.

Expression:

This formula contains two boolean expressions that evaluates to 1 or 0 in order to set calculated metric to zero and to avoid division by zero exception.

Expression:

Current average disk queue, the number of requests outstanding on the disk at the time the performance data is collected.

Preprocessing:

- JSONPATH: $[10]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.001

This item is the percentage of elapsed time that the selected disk drive was busy servicing read or writes requests.

Preprocessing:

- JSONPATH: $[9]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.1

Get contents of /sys/block/{#DEVNAME}/stat for disk stats.

Preprocessing:

- JAVASCRIPT: return JSON.stringify(value.trim().split(/ +/));

Rate of total read time counter. Used in r_await calculation

Preprocessing:

- JSONPATH: $[3]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.001

Rate of total write time counter. Used in w_await calculation

Preprocessing:

- JSONPATH: $[7]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.001

This trigger might indicate disk {#DEVNAME} saturation.

Manual close: YES

-

This macro is used as a threshold in interface utilization trigger.

-

-

Filter out loopbacks, nulls, docker veth links and docker0 bridge by default

Discovery of network interfaces.

Filter:

- {#IFNAME} MATCHES_REGEX {$NET.IF.IFNAME.MATCHES}

- {#IFNAME} NOT_MATCHES_REGEX {$NET.IF.IFNAME.NOT_MATCHES}

-

Preprocessing:

- CHANGE_PER_SECOND

- MULTIPLIER: 8

-

Preprocessing:

- CHANGE_PER_SECOND

- MULTIPLIER: 8

-

Preprocessing:

- CHANGE_PER_SECOND

-

Preprocessing:

- CHANGE_PER_SECOND

-

Preprocessing:

- CHANGE_PER_SECOND

-

Preprocessing:

- CHANGE_PER_SECOND

Reference: https://www.kernel.org/doc/Documentation/networking/operstates.txt

Preprocessing:

- JAVASCRIPT: The text is too long. Please see the template.

Indicates the interface protocol type as a decimal value.

See include/uapi/linux/if_arp.h for all possible values.

Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

Indicates the interface latest or current speed value. Value is an integer representing the link speed in bits/sec.

This attribute is only valid for interfaces that implement the ethtool get_link_ksettings method (mostly Ethernet).

Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net

Preprocessing:

- MULTIPLIER: 1000000

- DISCARD_UNCHANGED_HEARTBEAT: 1h

The network interface utilization is close to its estimated maximum bandwidth.

Recovery expression:

Manual close: YES

Depends on:

- Interface {#IFNAME}: Link down

Recovers when below 80% of {$IF.ERRORS.WARN:"{#IFNAME}"} threshold

Recovery expression:

Manual close: YES

Depends on:

- Interface {#IFNAME}: Link down

This trigger expression works as follows:

1. Can be triggered if operations status is down.

2. {$IFCONTROL:"{#IFNAME}"}=1 - user can redefine Context macro to value - 0. That marks this interface as not important. No new trigger will be fired if this interface is down.

3. {TEMPLATE_NAME:METRIC.diff()}=1) - trigger fires only if operational status was up(1) sometime before. (So, do not fire 'ethernal off' interfaces.)

WARNING: if closed manually - won't fire again on next poll, because of .diff.

Recovery expression:

Manual close: YES

This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close.

Recovery expression:

Manual close: YES

Depends on:

- Interface {#IFNAME}: Link down

-

-

-

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

System local time of the host.

System host name.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 12h

The information as normally returned by 'uname -a'.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 12h

Number of users who are currently logged in.

It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

-

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

Operating system architecture of the host.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

System uptime in 'N days, hh:mm:ss' format.

The host system time is different from the Zabbix server time.

Manual close: YES

System name has changed. Ack to close.

Manual close: YES

-

-

Depends on:

- Getting closer to process limit (over 80% used)

-

Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.

Manual close: YES

Depends on:

- System name has changed (new name: {ITEM.VALUE})

-

Manual close: YES

Depends on:

- Operating system description has changed

- System name has changed (new name: {ITEM.VALUE})

The host uptime is less than 10 minutes

Manual close: YES

-

Load per CPU considered sustainable. Tune if needed.

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

-

-

CPU utilization in %.

Preprocessing:

- JAVASCRIPT: //Calculate utilization return (100 - value)

The time the CPU has spent doing nothing.

The time the CPU has spent running the kernel and its processes.

The time the CPU has spent running users' processes that are not niced.

The time the CPU has spent running users' processes that have been niced.

Amount of time the CPU has been waiting for I/O to complete.

The amount of CPU 'stolen' from this virtual machine by the hypervisor for other tasks (such as running another virtual machine).

The amount of time the CPU has been servicing hardware interrupts.

The amount of time the CPU has been servicing software interrupts.

Guest time (time spent running a virtual CPU for a guest operating system).

Time spent running a niced guest (virtual CPU for guest operating systems under the control of the Linux kernel).

-

Preprocessing:

- CHANGE_PER_SECOND

-

Preprocessing:

- CHANGE_PER_SECOND

Per CPU load average is too high. Your system may be slow to respond.

CPU utilization is too high. The system might be slow to respond.

Depends on:

- Load average is too high (per CPU load over {$LOAD_AVG_PER_CPU.MAX.WARN} for 5m)

The critical threshold of the filesystem utilization.

The warning threshold of the filesystem utilization.

This macro is used in filesystems discovery. Can be overridden on the host or linked template level

This macro is used in filesystems discovery. Can be overridden on the host or linked template level

This macro is used in filesystems discovery. Can be overridden on the host or linked template level

This macro is used in filesystems discovery. Can be overridden on the host or linked template level

-

-

-

-

Discovery of file systems of different types.

Filter:

- A: {#FSTYPE} MATCHES_REGEX {$VFS.FS.FSTYPE.MATCHES}

- B: {#FSTYPE} NOT_MATCHES_REGEX {$VFS.FS.FSTYPE.NOT_MATCHES}

- C: {#FSNAME} MATCHES_REGEX {$VFS.FS.FSNAME.MATCHES}

- D: {#FSNAME} NOT_MATCHES_REGEX {$VFS.FS.FSNAME.NOT_MATCHES}

Overrides:

Skip metadata collection for dynamic FS
- {#FSTYPE} MATCHES_REGEX `^(btrfs

Used storage in Bytes

Total space in Bytes

Space utilization in % for {#FSNAME}

-

Two conditions should match: First, space utilization should be above {$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"}.

Second condition should be one of the following:

- The disk free space is less than {$VFS.FS.FREE.MIN.CRIT:"{#FSNAME}"}.

- The disk will be full in less than 24 hours.

Manual close: YES

Two conditions should match: First, space utilization should be above {$VFS.FS.PUSED.MAX.WARN:"{#FSNAME}"}.

Second condition should be one of the following:

- The disk free space is less than {$VFS.FS.FREE.MIN.WARN:"{#FSNAME}"}.

- The disk will be full in less than 24 hours.

Manual close: YES

Depends on:

- {#FSNAME}: Disk space is critically low (used > {$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"}%)

It may become impossible to write to disk if there are no index nodes left.

As symptoms, 'No space left on device' or 'Disk is full' errors may be seen even though free space is available.

It may become impossible to write to disk if there are no index nodes left.

As symptoms, 'No space left on device' or 'Disk is full' errors may be seen even though free space is available.

Depends on:

- {#FSNAME}: Running out of free inodes (free < {$VFS.FS.INODE.PFREE.MIN.CRIT:"{#FSNAME}"}%)

This macro is used as a threshold in memory available trigger.

This macro is used as a threshold in memory utilization trigger.

-

Memory used percentage is calculated as (100-pavailable)

Preprocessing:

- JAVASCRIPT: return (100-value);

Available memory as percentage of total. See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item.

Total memory in Bytes.

Available memory, in Linux, available = free + buffers + cache. On other platforms calculation may vary. See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item.

The total space of swap volume/file in bytes.

The free space of swap volume/file in bytes.

The free space of swap volume/file in percent.

The system is running out of free memory.

Depends on:

- Lack of available memory (<{$MEMORY.AVAILABLE.MIN} of {ITEM.VALUE2})

-

This trigger is ignored, if there is no swap configured.

Depends on:

- High memory utilization (>{$MEMORY.UTIL.MAX}% for 5m)

- Lack of available memory (<{$MEMORY.AVAILABLE.MIN} of {ITEM.VALUE2})

This macro is used in block devices discovery. Can be overridden on the host or linked template level

This macro is used in block devices discovery. Can be overridden on the host or linked template level

Disk read average response time (in ms) before the trigger would fire

Disk write average response time (in ms) before the trigger would fire

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

Filter:

- A: {#DEVTYPE} MATCHES_REGEX disk

- B: {#DEVNAME} MATCHES_REGEX {$VFS.DEV.DEVNAME.MATCHES}

- C: {#DEVNAME} NOT_MATCHES_REGEX {$VFS.DEV.DEVNAME.NOT_MATCHES}

r/s. The number (after merges) of read requests completed per second for the device.

Preprocessing:

- JSONPATH: $[0]

- CHANGE_PER_SECOND

w/s. The number (after merges) of write requests completed per second for the device.

Preprocessing:

- JSONPATH: $[4]

- CHANGE_PER_SECOND

This formula contains two boolean expressions that evaluates to 1 or 0 in order to set calculated metric to zero and to avoid division by zero exception.

Expression:

This formula contains two boolean expressions that evaluates to 1 or 0 in order to set calculated metric to zero and to avoid division by zero exception.

Expression:

Current average disk queue, the number of requests outstanding on the disk at the time the performance data is collected.

Preprocessing:

- JSONPATH: $[10]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.001

This item is the percentage of elapsed time that the selected disk drive was busy servicing read or writes requests.

Preprocessing:

- JSONPATH: $[9]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.1

Get contents of /sys/block/{#DEVNAME}/stat for disk stats.

Preprocessing:

- JAVASCRIPT: return JSON.stringify(value.trim().split(/ +/));

Rate of total read time counter. Used in r_await calculation

Preprocessing:

- JSONPATH: $[3]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.001

Rate of total write time counter. Used in w_await calculation

Preprocessing:

- JSONPATH: $[7]

- CHANGE_PER_SECOND

- MULTIPLIER: 0.001

This trigger might indicate disk {#DEVNAME} saturation.

Manual close: YES

-

This macro is used as a threshold in interface utilization trigger.

-

-

Filter out loopbacks, nulls, docker veth links and docker0 bridge by default

Discovery of network interfaces.

Filter:

- A: {#IFNAME} MATCHES_REGEX {$NET.IF.IFNAME.MATCHES}

- B: {#IFNAME} NOT_MATCHES_REGEX {$NET.IF.IFNAME.NOT_MATCHES}

Preprocessing:

- CHANGE_PER_SECOND

- MULTIPLIER: 8

Preprocessing:

- CHANGE_PER_SECOND

- MULTIPLIER: 8

Preprocessing:

- CHANGE_PER_SECOND

Preprocessing:

- CHANGE_PER_SECOND

Preprocessing:

- CHANGE_PER_SECOND

Preprocessing:

- CHANGE_PER_SECOND

Reference: https://www.kernel.org/doc/Documentation/networking/operstates.txt

Preprocessing:

- JAVASCRIPT: The text is too long. Please see the template.

Indicates the interface protocol type as a decimal value.

See include/uapi/linux/if_arp.h for all possible values.

Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

Indicates the interface latest or current speed value. Value is an integer representing the link speed in bits/sec.

This attribute is only valid for interfaces that implement the ethtool get_link_ksettings method (mostly Ethernet).

Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net

Preprocessing:

- MULTIPLIER: 1000000

- DISCARD_UNCHANGED_HEARTBEAT: 1h

The network interface utilization is close to its estimated maximum bandwidth.

Recovery expression:

Manual close: YES

Depends on:

- Interface {#IFNAME}: Link down

Recovers when below 80% of {$IF.ERRORS.WARN:"{#IFNAME}"} threshold

Recovery expression:

Manual close: YES

Depends on:

- Interface {#IFNAME}: Link down

This trigger expression works as follows:

1. Can be triggered if operations status is down.

2. {$IFCONTROL:"{#IFNAME}"}=1 - user can redefine Context macro to value - 0. That marks this interface as not important. No new trigger will be fired if this interface is down.

3. {TEMPLATE_NAME:METRIC.diff()}=1) - trigger fires only if operational status was up(1) sometime before. (So, do not fire 'ethernal off' interfaces.)

WARNING: if closed manually - won't fire again on next poll, because of .diff.

Recovery expression:

Manual close: YES

This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close.

Recovery expression:

Manual close: YES

Depends on:

- Interface {#IFNAME}: Link down

-

-

-

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

System local time of the host.

System host name.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 12h

The information as normally returned by 'uname -a'.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 12h

Number of users who are currently logged in.

It could be increased by using sysctl utility or modifying file /etc/sysctl.conf.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

It could be increased by using sysctl utility or modifying file /etc/sysctl.conf.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

-

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

Operating system architecture of the host.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

-

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

System uptime in 'N days, hh:mm:ss' format.

The host system time is different from the Zabbix server time.

Manual close: YES

System name has changed. Ack to close.

Manual close: YES

-

-

Depends on:

- Getting closer to process limit (over 80% used)

-

Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.

Manual close: YES

Depends on:

- System name has changed (new name: {ITEM.VALUE})

-

Manual close: YES

Depends on:

- Operating system description has changed

- System name has changed (new name: {ITEM.VALUE})

The host uptime is less than 10 minutes

Manual close: YES