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.

The warning threshold of the "Physical memory: Memory utilization" item.

This macro is used in memory discovery. Can be overridden on the host or linked template level if you need to filter out results.

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

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

This macro is used in memory discovery. Can be overridden on the host or linked template level if you need to filter out results.

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

Ignore notPresent(6)

Ignore down(2) administrative status

MIB: SNMPv2-MIB

The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

Preprocessing

• Custom multiplier: 0.01

MIB: HOST-RESOURCES-MIB

The amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.

Preprocessing

• Check for not supported value

  ⛔️Custom on fail: Set value to: 0

• Custom multiplier: 0.01

The item is used to collect all SNMP traps unmatched by other snmptrap items

MIB: SNMPv2-MIB

The physical location of this node (e.g., `telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.' was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

An administratively-assigned name for this managed node.By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

A textual description of the entity. This value should

include the full name and version identification of the system's hardware type, software operating-system, and

networking software.

Preprocessing

• Discard unchanged with heartbeat: 12h

Availability of SNMP checks on the host. The value of this item corresponds to availability icons in the host list.

Possible value:

0 - not available

1 - available

2 - unknown

MIB: HOST-RESOURCES-MIB

The average, over the last minute, of the percentage of time that processors was not idle.

Implementations may approximate this one minute smoothing period if necessary.

Preprocessing

• JSON Path: $..['{#CPU.UTIL}'].avg()

Uptime is less than 10 minutes.

• Windows: No SNMP data collection

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

SNMP is not available for polling. Please check device connectivity and SNMP settings.

• Windows: Unavailable by ICMP ping

Last three attempts returned timeout. Please check device connectivity.

• Windows: Unavailable by ICMP ping

• Windows: High ICMP ping loss
• Windows: Unavailable by ICMP ping

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

HOST-RESOURCES-MIB::hrStorage discovery with storage filter.

MIB: HOST-RESOURCES-MIB

The amount of the storage represented by this entry that is allocated, in units of hrStorageAllocationUnits.

Preprocessing

• Custom multiplier: {#ALLOC_UNITS}

MIB: HOST-RESOURCES-MIB

The size of the storage represented by this entry, in units of hrStorageAllocationUnits.

This object is writable to allow remote configuration of the size of the storage area in those cases where such an operation makes sense and is possible on the underlying system.

For example, the amount of main storage allocated to a buffer pool might be modified or the amount of disk space allocated to virtual storage might be modified.

Preprocessing

• Custom multiplier: {#ALLOC_UNITS}

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

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

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

• {#FSNAME}: Disk space is critically low

HOST-RESOURCES-MIB::hrStorage discovery with memory filter

MIB: HOST-RESOURCES-MIB

The amount of the storage represented by this entry that is allocated, in units of hrStorageAllocationUnits.

Preprocessing

• Custom multiplier: {#ALLOC_UNITS}

MIB: HOST-RESOURCES-MIB

The size of the storage represented by this entry, in units of hrStorageAllocationUnits.

This object is writable to allow remote configuration of the size of the storage area in those cases where such an operation makes sense and is possible on the underlying system.

For example, the amount of main memory allocated to a buffer pool might be modified or the amount of disk space allocated to virtual memory might be modified.

Preprocessing

• Custom multiplier: {#ALLOC_UNITS}

Memory utilization in %.

The system is running out of free memory.

Discovering interfaces from IF-MIB.

MIB: IF-MIB

The current operational state of the interface.

- The testing(3) state indicates that no operational packet scan be passed

- If ifAdminStatus is down(2) then ifOperStatus should be down(2)

- If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic

- It should change todormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection)

- It should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state

- It should remain in the notPresent(6) state if the interface has missing(typically, hardware) components.

MIB: IF-MIB

The total number of octets received on the interface,including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and another times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

• Custom multiplier: 8

MIB: IF-MIB

The total number of octets transmitted out of the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

• Custom multiplier: 8

MIB: IF-MIB

For packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

MIB: IF-MIB

For packet-oriented interfaces, the number of outbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of outbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

MIB: IF-MIB

The number of outbound packets which were chosen to be discarded

even though no errors had been detected to prevent their being deliverable to a higher-layer protocol.

One possible reason for discarding such a packet could be to free up buffer space.

Discontinuities in the value of this counter can occur at re-initialization of the management system,

and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

MIB: IF-MIB

The number of inbound packets which were chosen to be discarded

even though no errors had been detected to prevent their being deliverable to a higher-layer protocol.

One possible reason for discarding such a packet could be to free up buffer space.

Discontinuities in the value of this counter can occur at re-initialization of the management system,

and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

MIB: IF-MIB

The type of interface.

Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA),

through updating the syntax of the IANAifType textual convention.

Preprocessing

• Discard unchanged with heartbeat: 1d

MIB: IF-MIB

An estimate of the interface's current bandwidth in units of 1,000,000 bits per second. If this object reports a value of n' then the speed of the interface is somewhere in the range ofn-500,000' to`n+499,999'. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. For a sub-layer which has no concept of bandwidth, this object should be zero.

Preprocessing

• Custom multiplier: 1000000

• Discard unchanged with heartbeat: 1h

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.

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

• Interface {#IFNAME}({#IFALIAS}): Link down

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

• Interface {#IFNAME}({#IFALIAS}): Link down

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}({#IFALIAS}): Link down

No data timeout for active agents. Consider to keep it relatively high.

The critical threshold of the % Interrupt Time counter.

The threshold of the % Privileged Time counter.

The threshold of the Processor Queue Length counter.

The critical threshold of the CPU utilization expressed in %.

The warning threshold of the Free System Page Table Entries counter.

The warning threshold of the Memory Pages/sec counter.

The warning threshold of the Memory util item.

The warning threshold of the minimum free swap.

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.

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.

The critical threshold of the filesystem utilization in percent.

The warning threshold of the filesystem utilization in percent.

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

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

The warning threshold of disk time utilization in percent.

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

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

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

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

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

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

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

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

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

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

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

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

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.

The CPU utilization expressed in %.

The Processor Information\% Interrupt Time is the time the processor spends receiving and servicing

hardware interrupts during sample intervals. This value is an indirect indicator of the activity of

devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication

lines, network interface cards and other peripheral devices. This is an easy way to identify a potential

hardware failure. This should never be higher than 20%.

Context Switches/sec is the combined rate at which all processors on the computer are switched from one thread to another.

Context switches occur when a running thread voluntarily relinquishes the processor, is preempted by a higher priority ready thread, or switches between user-mode and privileged (kernel) mode to use an Executive or subsystem service.

It is the sum of Thread\Context Switches/sec for all threads running on all processors in the computer and is measured in numbers of switches.

There are context switch counters on the System and Thread objects. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.

The Processor Information\% Privileged Time counter shows the percent of time that the processor is spent

executing in Kernel (or Privileged) mode. Privileged mode includes services interrupts inside Interrupt

Service Routines (ISRs), executing Deferred Procedure Calls (DPCs), Device Driver calls and other kernel-mode

functions of the Windows® Operating System.

Processor DPC time is the time that a single processor spent receiving and servicing deferred procedure

calls (DPCs). DPCs are interrupts that run at a lower priority than standard interrupts. % DPC Time is a

component of % Privileged Time because DPCs are executed in privileged mode. If a high % DPC Time is

sustained, there may be a processor bottleneck or an application or hardware related issue that can

significantly diminish overall system performance.

The Processor Information\% User Time counter shows the percent of time that the processor(s) is spent executing

in User mode.

The number of logical processors available on the computer.

The Processor Queue Length shows the number of threads that are observed as delayed in the processor Ready Queue

and are waiting to be executed.

Used memory in bytes.

The total memory expressed in bytes.

Memory utilization in %.

Cache Bytes is the sum of the Memory\System Cache Resident Bytes, Memory\System Driver Resident Bytes,

Memory\System Code Resident Bytes, and Memory\Pool Paged Resident Bytes counters. This counter displays

the last observed value only; it is not an average.

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

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

Preprocessing

• JavaScript: return (100 - value)

The used space of swap volume/file in percent.

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

This indicates the number of page table entries not currently in use by the system. If the number is less

than 5,000, there may well be a memory leak or you running out of memory.

Page Faults/sec is the average number of pages faulted per second. It is measured in number of pages

faulted per second because only one page is faulted in each fault operation, hence this is also equal

to the number of page fault operations. This counter includes both hard faults (those that require

disk access) and soft faults (where the faulted page is found elsewhere in physical memory.) Most

processors can handle large numbers of soft faults without significant consequence. However, hard faults,

which require disk access, can cause significant delays.

This measures the rate at which pages are read from or written to disk to resolve hard page faults.

If the value is greater than 1,000, as a result of excessive paging, there may be a memory leak.

This measures the size, in bytes, of the non-paged pool. This is an area of system memory for objects

that cannot be written to disk but instead must remain in physical memory as long as they are allocated.

There is a possible memory leak if the value is greater than 175MB (or 100MB with the /3GB switch).

A typical Event ID 2019 is recorded in the system event log.

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

The local system time of the host.

The host name of the system.

Preprocessing

• Discard unchanged with heartbeat: 1d

System description of the host.

Preprocessing

• Discard unchanged with heartbeat: 1d

The number of processes.

The number of threads used by all running processes.

The architecture of the operating system.

Preprocessing

• Discard unchanged with heartbeat: 1d

Raw data of win32_networkadapter.

Preprocessing

• Discard unchanged with heartbeat: 1h

For active agents, nodata() with agent.ping is used with {$AGENT.NODATA_TIMEOUT} as time threshold.

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

"The CPU Interrupt Time in the last 5 minutes exceeds {$CPU.INTERRUPT.CRIT.MAX}%."
The Processor Information\% Interrupt Time is the time the processor spends receiving and servicing
hardware interrupts during sample intervals. This value is an indirect indicator of the activity of
devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication
lines, network interface cards and other peripheral devices. This is an easy way to identify a potential
hardware failure. This should never be higher than 20%.

• Windows: High CPU utilization

The CPU privileged time in the last 5 minutes exceeds {$CPU.PRIV.CRIT.MAX}%.

• Windows: High CPU utilization
• Windows: CPU interrupt time is too high

The CPU Queue Length in the last 5 minutes exceeds {$CPU.QUEUE.CRIT.MAX}. According to actual observations, PQL should not exceed the number of cores * 2. To fine-tune the conditions, use the macro {$CPU.QUEUE.CRIT.MAX }.

• Windows: High CPU utilization

The system is running out of free memory.

This trigger is ignored, if there is no swap configured

• Windows: High memory utilization

The Memory Free System Page Table Entries is less than {$MEM.PAGETABLECRIT.MIN} for 5 minutes. If the number is less than 5,000, there may well be a memory leak.

• Windows: High memory utilization

The Memory Pages/sec in the last 5 minutes exceeds {$MEM.PAGE_SEC.CRIT.MAX}. If the value is greater than 1,000, as a result of excessive paging, there may be a memory leak.

• Windows: High memory utilization

The device uptime is less than 10 minutes.

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

Discovery of file systems of different types.

Used storage in bytes

Total space in bytes

Space utilization 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.

• {#FSLABEL}({#FSNAME}): Disk space is critically low

Discovery of installed physical disks.

Preprocessing

• Replace: {#INSTANCE} -> {#DEVNAME}

Rate of read operations on the disk.

Rate of write operations on the disk.

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

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

Preprocessing

• JavaScript: return (100 - value)

The average time for read requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.

The average time for write requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.

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

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

The disk appears to be under heavy load.

• {#DEVNAME}: Disk read request responses are too high
• {#DEVNAME}: Disk write request responses are too high

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

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

Discovery of installed network interfaces.

Preprocessing

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

• Discard unchanged with heartbeat: 1h

Incoming traffic on the network interface.

Preprocessing

• Change per second

• Custom multiplier: 8

Outgoing traffic on the network interface.

Preprocessing

• Change per second

• Custom multiplier: 8

The number of incoming packets dropped on the network interface.

Preprocessing

• Change per second

The number of outgoing packets dropped on the network interface.

Preprocessing

• Change per second

The number of incoming packets with errors on the network interface.

Preprocessing

• Change per second

The number of outgoing packets with errors on the network interface.

Preprocessing

• Change per second

Estimated bandwidth of the network interface if any.

Preprocessing

• JSON Path: $[?(@.GUID == "{#IFGUID}")].Speed.first()

  ⛔️Custom on fail: Set value to: 0

• JavaScript: return (value=='9223372036854775807' ? 0 : value)

• Discard unchanged with heartbeat: 1h

The type of the network interface.

Preprocessing

• JSON Path: $[?(@.GUID == "{#IFGUID}")].AdapterTypeId.first()

• Discard unchanged with heartbeat: 1d

The operational status of the network interface.

Preprocessing

• JSON Path: $[?(@.GUID == "{#IFGUID}")].NetConnectionStatus.first()

• Discard unchanged with heartbeat: 1d

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

• Interface {#IFNAME}({#IFALIAS}): Link down

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

• Interface {#IFNAME}({#IFALIAS}): Link down

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}({#IFALIAS}): 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.

Discovery of Windows services of different types as defined in template's macros.

The service has a state other than "Running" for the last three times.

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

The critical threshold of the % Interrupt Time counter.

The threshold of the % Privileged Time counter.

The threshold of the Processor Queue Length counter.

The critical threshold of the CPU utilization expressed in %.

The warning threshold of the Free System Page Table Entries counter.

The warning threshold of the Memory Pages/sec counter.

The warning threshold of the Memory util item.

The warning threshold of the minimum free swap.

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.

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.

The critical threshold of the filesystem utilization in percent.

The warning threshold of the filesystem utilization in percent.

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

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

The warning threshold of disk time utilization in percent.

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

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

The upper threshold for difference of system time.

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

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

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

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

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

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

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

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

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

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

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

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.

The CPU utilization expressed in %.

The Processor Information\% Interrupt Time is the time the processor spends receiving and servicing

hardware interrupts during sample intervals. This value is an indirect indicator of the activity of

devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication

lines, network interface cards and other peripheral devices. This is an easy way to identify a potential

hardware failure. This should never be higher than 20%.

Context Switches/sec is the combined rate at which all processors on the computer are switched from one thread to another.

Context switches occur when a running thread voluntarily relinquishes the processor, is preempted by a higher priority ready thread, or switches between user-mode and privileged (kernel) mode to use an Executive or subsystem service.

It is the sum of Thread\Context Switches/sec for all threads running on all processors in the computer and is measured in numbers of switches.

There are context switch counters on the System and Thread objects. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.

The Processor Information\% Privileged Time counter shows the percent of time that the processor is spent

executing in Kernel (or Privileged) mode. Privileged mode includes services interrupts inside Interrupt

Service Routines (ISRs), executing Deferred Procedure Calls (DPCs), Device Driver calls and other kernel-mode

functions of the Windows® Operating System.

Processor DPC time is the time that a single processor spent receiving and servicing deferred procedure

calls (DPCs). DPCs are interrupts that run at a lower priority than standard interrupts. % DPC Time is a

component of % Privileged Time because DPCs are executed in privileged mode. If a high % DPC Time is

sustained, there may be a processor bottleneck or an application or hardware related issue that can

significantly diminish overall system performance.

The Processor Information\% User Time counter shows the percent of time that the processor(s) is spent executing

in User mode.

The number of logical processors available on the computer.

The Processor Queue Length shows the number of threads that are observed as delayed in the processor Ready Queue

and are waiting to be executed.

Used memory in bytes.

The total memory expressed in bytes.

Memory utilization in %.

Cache Bytes is the sum of the Memory\System Cache Resident Bytes, Memory\System Driver Resident Bytes,

Memory\System Code Resident Bytes, and Memory\Pool Paged Resident Bytes counters. This counter displays

the last observed value only; it is not an average.

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

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

Preprocessing

• JavaScript: return (100 - value)

The used space of swap volume/file in percent.

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

This indicates the number of page table entries not currently in use by the system. If the number is less

than 5,000, there may well be a memory leak or you running out of memory.

Page Faults/sec is the average number of pages faulted per second. It is measured in number of pages

faulted per second because only one page is faulted in each fault operation, hence this is also equal

to the number of page fault operations. This counter includes both hard faults (those that require

disk access) and soft faults (where the faulted page is found elsewhere in physical memory.) Most

processors can handle large numbers of soft faults without significant consequence. However, hard faults,

which require disk access, can cause significant delays.

This measures the rate at which pages are read from or written to disk to resolve hard page faults.

If the value is greater than 1,000, as a result of excessive paging, there may be a memory leak.

This measures the size, in bytes, of the non-paged pool. This is an area of system memory for objects

that cannot be written to disk but instead must remain in physical memory as long as they are allocated.

There is a possible memory leak if the value is greater than 175MB (or 100MB with the /3GB switch).

A typical Event ID 2019 is recorded in the system event log.

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

The local system time of the host.

The host name of the system.

Preprocessing

• Discard unchanged with heartbeat: 1d

System description of the host.

Preprocessing

• Discard unchanged with heartbeat: 1d

The number of processes.

The number of threads used by all running processes.

The architecture of the operating system.

Preprocessing

• Discard unchanged with heartbeat: 1d

Raw data of win32_networkadapter.

Preprocessing

• Discard unchanged with heartbeat: 1h

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

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

"The CPU Interrupt Time in the last 5 minutes exceeds {$CPU.INTERRUPT.CRIT.MAX}%."
The Processor Information\% Interrupt Time is the time the processor spends receiving and servicing
hardware interrupts during sample intervals. This value is an indirect indicator of the activity of
devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication
lines, network interface cards and other peripheral devices. This is an easy way to identify a potential
hardware failure. This should never be higher than 20%.

• Windows: High CPU utilization

The CPU privileged time in the last 5 minutes exceeds {$CPU.PRIV.CRIT.MAX}%.

• Windows: High CPU utilization
• Windows: CPU interrupt time is too high

The CPU Queue Length in the last 5 minutes exceeds {$CPU.QUEUE.CRIT.MAX}. According to actual observations, PQL should not exceed the number of cores * 2. To fine-tune the conditions, use the macro {$CPU.QUEUE.CRIT.MAX }.

• Windows: High CPU utilization

The system is running out of free memory.

This trigger is ignored, if there is no swap configured

• Windows: High memory utilization

The Memory Free System Page Table Entries is less than {$MEM.PAGETABLECRIT.MIN} for 5 minutes. If the number is less than 5,000, there may well be a memory leak.

• Windows: High memory utilization

The Memory Pages/sec in the last 5 minutes exceeds {$MEM.PAGE_SEC.CRIT.MAX}. If the value is greater than 1,000, as a result of excessive paging, there may be a memory leak.

• Windows: High memory utilization

The device 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.

Discovery of file systems of different types.

Used storage in bytes

Total space in bytes

Space utilization 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.

• {#FSLABEL}({#FSNAME}): Disk space is critically low

Discovery of installed physical disks.

Preprocessing

• Replace: {#INSTANCE} -> {#DEVNAME}

Rate of read operations on the disk.

Rate of write operations on the disk.

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

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

Preprocessing

• JavaScript: return (100 - value)

The average time for read requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.

The average time for write requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.

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

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

The disk appears to be under heavy load.

• {#DEVNAME}: Disk read request responses are too high
• {#DEVNAME}: Disk write request responses are too high

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

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

Discovery of installed network interfaces.

Preprocessing

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

• Discard unchanged with heartbeat: 1h

Incoming traffic on the network interface.

Preprocessing

• Change per second

• Custom multiplier: 8

Outgoing traffic on the network interface.

Preprocessing

• Change per second

• Custom multiplier: 8

The number of incoming packets dropped on the network interface.

Preprocessing

• Change per second

The number of outgoing packets dropped on the network interface.

Preprocessing

• Change per second

The number of incoming packets with errors on the network interface.

Preprocessing

• Change per second

The number of outgoing packets with errors on the network interface.

Preprocessing

• Change per second

Estimated bandwidth of the network interface if any.

Preprocessing

• JSON Path: $[?(@.GUID == "{#IFGUID}")].Speed.first()

  ⛔️Custom on fail: Set value to: 0

• JavaScript: return (value=='9223372036854775807' ? 0 : value)

• Discard unchanged with heartbeat: 1h

The type of the network interface.

Preprocessing

• JSON Path: $[?(@.GUID == "{#IFGUID}")].AdapterTypeId.first()

• Discard unchanged with heartbeat: 1d

The operational status of the network interface.

Preprocessing

• JSON Path: $[?(@.GUID == "{#IFGUID}")].NetConnectionStatus.first()

• Discard unchanged with heartbeat: 1d

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

• Interface {#IFNAME}({#IFALIAS}): Link down

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

• Interface {#IFNAME}({#IFALIAS}): Link down

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}({#IFALIAS}): 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.

Discovery of Windows services of different types as defined in template's macros.

The service has a state other than "Running" for the last three times.

The timeout after which the agent is considered unavailable. It works only for the agents reachable from Zabbix server/proxy (in passive mode).

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

The number of processes in a running state.

The total number of processes in any state.

Preprocessing

• Change per second

The processor load is calculated as the system CPU load divided by the number of CPU cores.

The processor load is calculated as the system CPU load divided by the number of CPU cores.

The processor load is calculated as the system CPU load divided by the number of CPU cores.

Preprocessing

• Change per second

The time the CPU has spent doing nothing.

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

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.

A host name of the system.

Preprocessing

• Discard unchanged with heartbeat: 1d

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

Preprocessing

• Discard unchanged with heartbeat: 1d

The number of users who are currently logged in.

Preprocessing

• Discard unchanged with heartbeat: 1h

The available memory is defined as free+cached+buffers memory.

Preprocessing

• Discard unchanged with heartbeat: 1d

Preprocessing

• Discard unchanged with heartbeat: 1d

Monitoring agent availability status

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

The OS spends significant time waiting for the I/O (input/output) operations. It could be an indicator of performance issues with the storage system.

It probably means that the systems requires more physical memory.

For passive checks only the availability of the agents and a host is used with {$AGENT.TIMEOUT} as the time threshold.

The discovery of network interfaces as defined in the global regular expression "Network interfaces for discovery".

Preprocessing

• Change per second

• Custom multiplier: 8

Preprocessing

• Change per second

• Custom multiplier: 8

Discovery of different types of file systems as defined in the global regular expression "File systems for discovery".

The timeout after which the agent is considered unavailable. It works only for the agents reachable from Zabbix server/proxy (in passive mode).

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

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

The number of processes in a running state.

The total number of processes in any state.

Preprocessing

• Change per second:

The processor load is calculated as the system CPU load divided by the number of CPU cores.

The processor load is calculated as the system CPU load divided by the number of CPU cores.

The processor load is calculated as the system CPU load divided by the number of CPU cores.

Preprocessing

• Change per second:

The time the CPU has spent doing nothing.

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

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

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.

A host name of the system.

Preprocessing

• Discard unchanged with heartbeat: 1d

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

Preprocessing

• Discard unchanged with heartbeat: 1d

The number of users who are currently logged in.

Preprocessing

• Discard unchanged with heartbeat: 1h

The available memory is defined as free+cached+buffers memory.

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 the availability check.

Monitoring the availability status of the agent.

It probably means that the systems requires more physical memory.

For passive checks only the availability of the agents and a host is used with {$AGENT.TIMEOUT} as the time threshold.

The discovery of network interfaces as defined in the global regular expression "Network interfaces for discovery".

Preprocessing

• Change per second:

• Custom multiplier: 8

Preprocessing

• Change per second:

• Custom multiplier: 8

Discovery of different types of file systems as defined in the global regular expression "File systems for discovery".

The timeout after which the agent is considered unavailable. It works only for the agents reachable from Zabbix server/proxy (in passive mode).

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

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

Preprocessing

• Change per second

• Custom multiplier: 8

Preprocessing

• Change per second

• Custom multiplier: 8

The processor load is calculated as the system CPU load divided by the number of CPU cores.

The processor load is calculated as the system CPU load divided by the number of CPU cores.

The processor load is calculated as the system CPU load divided by the number of CPU cores.

A host name of the system.

Preprocessing

• Discard unchanged with heartbeat: 1d

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

Preprocessing

• Discard unchanged with heartbeat: 1d

The number of users who are currently logged in.

Preprocessing

• Discard unchanged with heartbeat: 1h

The available memory is defined as free+cached+buffers memory.

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 the availability check.

Monitoring the availability status of the agent.

For passive checks only the availability of the agents and a host is used with {$AGENT.TIMEOUT} as the time threshold.

Discovery of different types of file systems as defined in the global regular expression "File systems for discovery".

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

Load per CPU considered sustainable. Tune if needed.

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

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

Ignore notPresent(6)

Ignore down(2) administrative status

Please note that memory utilization is a rough estimate, since memory available is calculated as free+buffers+cached, which is not 100% accurate, but the best we can get using SNMP.

MIB: UCD-SNMP-MIB

Preprocessing

• Custom multiplier: 1024

MIB: UCD-SNMP-MIB

Memory used by kernel buffers (Buffers in /proc/meminfo).

Preprocessing

• Custom multiplier: 1024

MIB: UCD-SNMP-MIB

Memory used by the page cache and slabs (Cached and Slab in /proc/meminfo).

Preprocessing

• Custom multiplier: 1024

MIB: UCD-SNMP-MIB

The total memory expressed in bytes.

Preprocessing

• Custom multiplier: 1024

Please note that memory utilization is a rough estimate, since memory available is calculated as free+buffers+cached, which is not 100% accurate, but the best we can get using SNMP.

MIB: UCD-SNMP-MIB

The total amount of swap space configured for this host.

Preprocessing

• Custom multiplier: 1024

MIB: UCD-SNMP-MIB

The amount of swap space currently unused or available.

Preprocessing

• Custom multiplier: 1024

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

MIB: UCD-SNMP-MIB

MIB: UCD-SNMP-MIB

MIB: UCD-SNMP-MIB

MIB: HOST-RESOURCES-MIB

Count the number of CPU cores by counting number of cores discovered in hrProcessorTable using LLD

Preprocessing

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

Preprocessing

• Change per second

Preprocessing

• Change per second

MIB: SNMPv2-MIB

The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

Preprocessing

• Custom multiplier: 0.01

MIB: HOST-RESOURCES-MIB

The amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.

Preprocessing

• Check for not supported value

  ⛔️Custom on fail: Set value to: 0

• Custom multiplier: 0.01

The item is used to collect all SNMP traps unmatched by other snmptrap items

MIB: SNMPv2-MIB

The physical location of this node (e.g., `telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.' was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

An administratively-assigned name for this managed node.By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

A textual description of the entity. This value should

include the full name and version identification of the system's hardware type, software operating-system, and

networking software.

Preprocessing

• Discard unchanged with heartbeat: 12h

Availability of SNMP checks on the host. The value of this item corresponds to availability icons in the host list.

Possible value:

0 - not available

1 - available

2 - unknown

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 load average per CPU is too high. The system may be slow to respond.

Uptime is less than 10 minutes.

• Linux: No SNMP data collection

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

SNMP is not available for polling. Please check device connectivity and SNMP settings.

• Linux: Unavailable by ICMP ping

Last three attempts returned timeout. Please check device connectivity.

• Linux: Unavailable by ICMP ping

• Linux: High ICMP ping loss
• Linux: Unavailable by ICMP ping

Block devices are discovered from UCD-DISKIO-MIB::diskIOTable (http://net-snmp.sourceforge.net/docs/mibs/ucdDiskIOMIB.html#diskIOTable)

MIB: UCD-DISKIO-MIB

The number of read accesses from this device since boot.

Preprocessing

• Change per second

MIB: UCD-DISKIO-MIB

The number of write accesses from this device since boot.

Preprocessing

• Change per second

MIB: UCD-DISKIO-MIB

The 1 minute average load of disk (%)

This discovery will create set of per core CPU metrics from UCD-SNMP-MIB, using {#CPU.COUNT} in preprocessing. That's the only reason why LLD is used.

Preprocessing

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

MIB: UCD-SNMP-MIB

The time the CPU has spent doing nothing.

Preprocessing

• Change per second

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

MIB: UCD-SNMP-MIB

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

Preprocessing

• Change per second

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

MIB: UCD-SNMP-MIB

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

Preprocessing

• Change per second

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

MIB: UCD-SNMP-MIB

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

Preprocessing

• Change per second

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

MIB: UCD-SNMP-MIB

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

Preprocessing

• Change per second

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

MIB: UCD-SNMP-MIB

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

Preprocessing

• Change per second

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

MIB: UCD-SNMP-MIB

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

Preprocessing

• Change per second

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

MIB: UCD-SNMP-MIB

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

Preprocessing

• Change per second

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

MIB: UCD-SNMP-MIB

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

Preprocessing

• Change per second

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

MIB: UCD-SNMP-MIB

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

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

The CPU utilization expressed in %.

Preprocessing

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

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

HOST-RESOURCES-MIB::hrStorage discovery with storage filter

MIB: HOST-RESOURCES-MIB

The amount of the storage represented by this entry that is allocated, in units of hrStorageAllocationUnits.

Preprocessing

• Custom multiplier: {#ALLOC_UNITS}

MIB: HOST-RESOURCES-MIB

The size of the storage represented by this entry, in units of hrStorageAllocationUnits.

This object is writable to allow remote configuration of the size of the storage area in those cases where such an operation makes sense and is possible on the underlying system.

For example, the amount of main storage allocated to a buffer pool might be modified or the amount of disk space allocated to virtual storage might be modified.

Preprocessing

• Custom multiplier: {#ALLOC_UNITS}

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

MIB: UCD-SNMP-MIB

If having problems collecting this item make sure access to UCD-SNMP-MIB is allowed.

Preprocessing

• JavaScript: return (100-value);

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

Discovering interfaces from IF-MIB.

MIB: IF-MIB

The current operational state of the interface.

- The testing(3) state indicates that no operational packet scan be passed

- If ifAdminStatus is down(2) then ifOperStatus should be down(2)

- If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic

- It should change todormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection)

- It should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state

- It should remain in the notPresent(6) state if the interface has missing(typically, hardware) components.

MIB: IF-MIB

The total number of octets received on the interface, including framing characters. This object is a 64-bit version of ifInOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

• Custom multiplier: 8

MIB: IF-MIB

The total number of octets transmitted out of the interface, including framing characters. This object is a 64-bit version of ifOutOctets.Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

• Custom multiplier: 8

MIB: IF-MIB

For packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

MIB: IF-MIB

For packet-oriented interfaces, the number of outbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of outbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

MIB: IF-MIB

The number of outbound packets which were chosen to be discarded

even though no errors had been detected to prevent their being deliverable to a higher-layer protocol.

One possible reason for discarding such a packet could be to free up buffer space.

Discontinuities in the value of this counter can occur at re-initialization of the management system,

and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

MIB: IF-MIB

The number of inbound packets which were chosen to be discarded

even though no errors had been detected to prevent their being deliverable to a higher-layer protocol.

One possible reason for discarding such a packet could be to free up buffer space.

Discontinuities in the value of this counter can occur at re-initialization of the management system,

and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second

MIB: IF-MIB

The type of interface.

Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA),

through updating the syntax of the IANAifType textual convention.

Preprocessing

• Discard unchanged with heartbeat: 1d

MIB: IF-MIB

An estimate of the interface's current bandwidth in units of 1,000,000 bits per second. If this object reports a value of n' then the speed of the interface is somewhere in the range ofn-500,000' to`n+499,999'. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. For a sub-layer which has no concept of bandwidth, this object should be zero.

Preprocessing

• Custom multiplier: 1000000

• Discard unchanged with heartbeat: 1h

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.

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

• Interface {#IFNAME}({#IFALIAS}): Link down

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

• Interface {#IFNAME}({#IFALIAS}): Link down

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}({#IFALIAS}): Link down

Discovering interfaces from IF-MIB and EtherLike-MIB. Interfaces with up(1) Operational Status are discovered.

Preprocessing

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

MIB: EtherLike-MIB

The current mode of operation of the MAC

entity. 'unknown' indicates that the current

duplex mode could not be determined.

Management control of the duplex mode is

accomplished through the MAU MIB. When

an interface does not support autonegotiation,

or when autonegotiation is not enabled, the

duplex mode is controlled using

ifMauDefaultType. When autonegotiation is

supported and enabled, duplex mode is controlled

using ifMauAutoNegAdvertisedBits. In either

case, the currently operating duplex mode is

reflected both in this object and in ifMauType.

Note that this object provides redundant

information with ifMauType. Normally, redundant

objects are discouraged. However, in this

instance, it allows a management application to

determine the duplex status of an interface

without having to know every possible value of

ifMauType. This was felt to be sufficiently

valuable to justify the redundancy.

Reference: [IEEE 802.3 Std.], 30.3.1.1.32,aDuplexStatus.

Please check autonegotiation settings and cabling

The upper threshold for difference of system time.

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

Load per CPU considered sustainable. Tune if needed.

The hostname or IP address of the node_exporter host.

TCP Port node_exporter is listening on.

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

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

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.

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.

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.

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

Ignore notpresent(1).

Preprocessing

• Prometheus pattern: node_exporter_build_info label version

• Discard unchanged with heartbeat: 1d

Preprocessing

• Prometheus pattern: VALUE({__name__=~"^node_boot_time(?:_seconds)?$"})

The local system time of the host.

Preprocessing

• Prometheus pattern: VALUE({__name__=~"^node_time(?:_seconds)?$"})

The host name of the system.

Preprocessing

• Prometheus pattern: node_uname_info label nodename

• Discard unchanged with heartbeat: 1d

Labeled system information as provided by the uname system call.

Preprocessing

• Prometheus to JSON: node_uname_info

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

• Discard unchanged with heartbeat: 1d

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

Preprocessing

• Prometheus pattern: VALUE(node_filefd_maximum)

• Discard unchanged with heartbeat: 1d

Preprocessing

• Prometheus pattern: VALUE(node_filefd_allocated)

Preprocessing

• Discard unchanged with heartbeat: 1d

The architecture of the operating system.

Preprocessing

• Prometheus pattern: node_uname_info label machine

• Discard unchanged with heartbeat: 1d

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

Preprocessing

• Prometheus pattern: VALUE({__name__=~"^node_boot_time(?:_seconds)?$"})

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

Preprocessing

• Prometheus pattern: VALUE(node_load1)

Preprocessing

• Prometheus pattern: VALUE(node_load5)

Preprocessing

• Prometheus pattern: VALUE(node_load15)

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

The time the CPU has spent doing nothing.

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

• Change per second

• Custom multiplier: 100

The CPU utilization expressed in %.

Preprocessing

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

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

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

• Change per second

• Custom multiplier: 100

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

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

• Change per second

• Custom multiplier: 100

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

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

• Change per second

• Custom multiplier: 100

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

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

• Change per second

• Custom multiplier: 100

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

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

• Change per second

• Custom multiplier: 100

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

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

• Change per second

• Custom multiplier: 100

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

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

• Change per second

• Custom multiplier: 100

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

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

• Change per second

• Custom multiplier: 100

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

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

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

• Change per second

• Custom multiplier: 100

Preprocessing

• Prometheus pattern: VALUE({__name__=~"node_intr"})

• Change per second

Preprocessing

• Prometheus pattern: VALUE({__name__=~"node_context_switches"})

• Change per second

Memory used percentage is calculated as (total-available)/total*100.

The total memory expressed in bytes.

Preprocessing

• Prometheus pattern: VALUE({__name__=~"node_memory_MemTotal"})

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.

Preprocessing

• Prometheus pattern: VALUE({__name__=~"node_memory_MemAvailable"})

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

Preprocessing

• Prometheus pattern: VALUE({__name__=~"node_memory_SwapTotal"})

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

Preprocessing

• Prometheus pattern: VALUE({__name__=~"node_memory_SwapFree"})

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

Failed to fetch system metrics from node_exporter in time.

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: Running out of file descriptors

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 device uptime is less than 10 minutes.

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

Discovery of network interfaces. Requires node_exporter v0.18 and up.

Preprocessing

• Prometheus to JSON: {__name__=~"^node_network_info$"}

Preprocessing

• Prometheus pattern: VALUE(node_network_receive_bytes_total{device="{#IFNAME}"})

• Change per second

• Custom multiplier: 8

Preprocessing

• Prometheus pattern: VALUE(node_network_transmit_bytes_total{device="{#IFNAME}"})

• Change per second

• Custom multiplier: 8

Preprocessing

• Prometheus pattern: VALUE(node_network_transmit_errs_total{device="{#IFNAME}"})

• Change per second

Preprocessing

• Prometheus pattern: VALUE(node_network_receive_errs_total{device="{#IFNAME}"})

• Change per second

Preprocessing

• Prometheus pattern: VALUE(node_network_receive_drop_total{device="{#IFNAME}"})

• Change per second

Preprocessing

• Prometheus pattern: VALUE(node_network_transmit_drop_total{device="{#IFNAME}"})

• Change per second

Sets value to 0 if metric is missing in node_exporter output.

Preprocessing

• Prometheus pattern: VALUE(node_network_speed_bytes{device="{#IFNAME}"})

  ⛔️Custom on fail: Set value to: 0

• Custom multiplier: 8

nodenetworkprotocoltype protocoltype value of /sys/class/net/.

Preprocessing

• Prometheus pattern: VALUE(node_network_protocol_type{device="{#IFNAME}"})

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

Preprocessing

• Prometheus pattern: node_network_info{device="{#IFNAME}"} label operstate

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

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

• Interface {#IFNAME}({#IFALIAS}): Link down

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

• Interface {#IFNAME}({#IFALIAS}): Link down

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}({#IFALIAS}): Link down

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}({#IFALIAS}): 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.

Discovery of file systems of different types.

Preprocessing

• Prometheus to JSON: The text is too long. Please see the template.

Preprocessing

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

Total space in bytes

Preprocessing

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

Used storage in bytes

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

Preprocessing

• Prometheus to JSON: {__name__=~"node_filesystem_files.*",mountpoint="{#FSNAME}"}

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

• {#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

• Prometheus to JSON: node_disk_io_now{device=~".+"}

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

Preprocessing

• Prometheus pattern: VALUE(node_disk_reads_completed_total{device="{#DEVNAME}"})

• Change per second

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

Preprocessing

• Prometheus pattern: VALUE(node_disk_writes_completed_total{device="{#DEVNAME}"})

• Change per second

Rate of total read time counter. Used in r_await calculation.

Preprocessing

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

• Change per second

Rate of total write time counter. Used in w_await calculation.

Preprocessing

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

• 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.

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.

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

Preprocessing

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

• Change per second

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

Preprocessing

• Prometheus pattern: VALUE(node_disk_io_time_seconds_total{device="{#DEVNAME}"})

• Change per second

• Custom multiplier: 100

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

No data timeout for active agents. Consider to keep it relatively high.

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.

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.

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 active agents, nodata() with agent.ping is used with {$AGENT.NODATA_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 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

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