No data timeout for active agents. Consider to keep it relatively high.
|`30m`| |{$AGENT.TIMEOUT}|Timeout after which agent is considered unavailable.
|`5m`| |{$CPU.INTERRUPT.CRIT.MAX}|The critical threshold of the % Interrupt Time counter.
|`50`| |{$CPU.PRIV.CRIT.MAX}|The threshold of the % Privileged Time counter.
|`30`| |{$CPU.QUEUE.CRIT.MAX}|The threshold of the Processor Queue Length counter.
|`3`| |{$CPU.UTIL.CRIT}|The critical threshold of the CPU utilization expressed in %.
|`90`| |{$MEM.PAGE_TABLE_CRIT.MIN}|The warning threshold of the Free System Page Table Entries counter.
|`5000`| |{$MEM.PAGE_SEC.CRIT.MAX}|The warning threshold of the Memory Pages/sec counter.
|`1000`| |{$MEMORY.UTIL.MAX}|The warning threshold of the Memory util item.
|`90`| |{$SWAP.PFREE.MIN.WARN}|The warning threshold of the minimum free swap.
|`20`| |{$VFS.FS.FSNAME.MATCHES}|This macro is used in filesystems discovery. Can be overridden on the host or linked template level.
|`.*`| |{$VFS.FS.FSNAME.NOT_MATCHES}|This macro is used in filesystems discovery. Can be overridden on the host or linked template level.
|`^(?:/dev\|/sys\|/run\|/proc\|.+/shm$)`| |{$VFS.FS.FSTYPE.MATCHES}|This macro is used in filesystems discovery. Can be overridden on the host or linked template level.
|`.*`| |{$VFS.FS.FSTYPE.NOT_MATCHES}|This macro is used in filesystems discovery. Can be overridden on the host or linked template level.
|`^\s$`| |{$VFS.FS.FSDRIVETYPE.MATCHES}|This macro is used in filesystems discovery. Can be overridden on the host or linked template level.
|`fixed`| |{$VFS.FS.FSDRIVETYPE.NOT_MATCHES}|This macro is used in filesystems discovery. Can be overridden on the host or linked template level.
|`^\s$`| |{$VFS.FS.PUSED.MAX.CRIT}|The critical threshold of the filesystem utilization in percent.
|`90`| |{$VFS.FS.PUSED.MAX.WARN}|The warning threshold of the filesystem utilization in percent.
|`80`| |{$VFS.FS.FREE.MIN.CRIT}|The critical threshold of the filesystem utilization.
|`5G`| |{$VFS.FS.FREE.MIN.WARN}|The warning threshold of the filesystem utilization.
|`10G`| |{$VFS.DEV.DEVNAME.MATCHES}|This macro is used in physical disks discovery. Can be overridden on the host or linked template level.
|`.*`| |{$VFS.DEV.DEVNAME.NOT_MATCHES}|This macro is used in physical disks discovery. Can be overridden on the host or linked template level.
|`_Total`| |{$VFS.DEV.UTIL.MAX.WARN}|The warning threshold of disk time utilization in percent.
|`95`| |{$VFS.DEV.READ.AWAIT.WARN}|Disk read average response time (in s) before the trigger would fire.
|`0.02`| |{$VFS.DEV.WRITE.AWAIT.WARN}|Disk write average response time (in s) before the trigger would fire.
|`0.02`| |{$SYSTEM.FUZZYTIME.MAX}|The threshold for difference of system time in seconds.
|`60`| |{$IFCONTROL}||`1`| |{$NET.IF.IFNAME.MATCHES}|This macro is used in Network interface discovery. Can be overridden on the host or linked template level.
|`.*`| |{$NET.IF.IFNAME.NOT_MATCHES}|This macro is used in Network interface discovery. Can be overridden on the host or linked template level.
|`Macro too long. Please see the template.`| |{$NET.IF.IFALIAS.MATCHES}|This macro is used in Network interface discovery. Can be overridden on the host or linked template level.
|`.*`| |{$NET.IF.IFALIAS.NOT_MATCHES}|This macro is used in Network interface discovery. Can be overridden on the host or linked template level.
|`CHANGE_THIS`| |{$NET.IF.IFDESCR.MATCHES}|This macro is used in Network interface discovery. Can be overridden on the host or linked template level.
|`.*`| |{$NET.IF.IFDESCR.NOT_MATCHES}|This macro is used in Network interface discovery. Can be overridden on the host or linked template level.
|`CHANGE_THIS`| |{$IF.UTIL.MAX}||`90`| |{$IF.ERRORS.WARN}||`2`| |{$SERVICE.NAME.MATCHES}|This macro is used in Service discovery. Can be overridden on the host or linked template level.
|`^.*$`| |{$SERVICE.NAME.NOT_MATCHES}|This macro is used in Service discovery. Can be overridden on the host or linked template level.
|`Macro too long. Please see the template.`| |{$SERVICE.STARTUPNAME.MATCHES}|This macro is used in Service discovery. Can be overridden on the host or linked template level.
|`^(?:automatic\|automatic delayed)$`| |{$SERVICE.STARTUPNAME.NOT_MATCHES}|This macro is used in Service discovery. Can be overridden on the host or linked template level.
|`^(?:manual\|disabled)$`| ### Items |Name|Description|Type|Key and additional info| |----|-----------|----|-----------------------| |Windows: Version of Zabbix agent running||Zabbix agent (active)|agent.version**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.
|Zabbix agent (active)|agent.ping| |Windows: Active agent availability|Availability of active checks on the host. The value of this item corresponds to availability icons in the host list.
Possible value:
0 - unknown
1 - available
2 - not available
|Zabbix internal|zabbix[host,active_agent,available]| |Windows: CPU utilization|The CPU utilization expressed in %.
|Zabbix agent (active)|system.cpu.util| |Windows: CPU interrupt time|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%.
|Zabbix agent (active)|perf_counter_en["\Processor Information(_total)\% Interrupt Time"]| |Windows: Context switches per second|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.
|Zabbix agent (active)|perf_counter_en["\System\Context Switches/sec"]| |Windows: CPU privileged time|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.
|Zabbix agent (active)|perf_counter_en["\Processor Information(_total)\% Privileged Time"]| |Windows: CPU DPC time|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.
|Zabbix agent (active)|perf_counter_en["\Processor Information(_total)\% DPC Time"]| |Windows: CPU user time|The Processor Information\% User Time counter shows the percent of time that the processor(s) is spent executing
in User mode.
|Zabbix agent (active)|perf_counter_en["\Processor Information(_total)\% User Time"]| |Windows: Number of cores|The number of logical processors available on the computer.
|Zabbix agent (active)|wmi.get[root/cimv2,"Select NumberOfLogicalProcessors from Win32_ComputerSystem"]| |Windows: CPU queue length|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.
|Zabbix agent (active)|perf_counter_en["\System\Processor Queue Length"]| |Windows: Used memory|Used memory in bytes.
|Zabbix agent (active)|vm.memory.size[used]| |Windows: Total memory|The total memory expressed in bytes.
|Zabbix agent (active)|vm.memory.size[total]| |Windows: Memory utilization|Memory utilization in %.
|Calculated|vm.memory.util| |Windows: Cache bytes|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.
|Zabbix agent (active)|perf_counter_en["\Memory\Cache Bytes"]| |Windows: Free swap space|The free space of the swap volume/file expressed in bytes.
|Calculated|system.swap.free| |Windows: Free swap space in %|The free space of the swap volume/file expressed in %.
|Dependent item|system.swap.pfree**Preprocessing**
JavaScript: `return (100 - value)`
The used space of swap volume/file in percent.
|Zabbix agent (active)|perf_counter_en["\Paging file(_Total)\% Usage"]| |Windows: Total swap space|The total space of the swap volume/file expressed in bytes.
|Zabbix agent (active)|system.swap.size[,total]| |Windows: Free system page table entries|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.
|Zabbix agent (active)|perf_counter_en["\Memory\Free System Page Table Entries"]| |Windows: Memory page faults per second|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.
|Zabbix agent (active)|perf_counter_en["\Memory\Page Faults/sec"]| |Windows: Memory pages per second|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.
|Zabbix agent (active)|perf_counter_en["\Memory\Pages/sec"]| |Windows: Memory pool non-paged|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.
|Zabbix agent (active)|perf_counter_en["\Memory\Pool Nonpaged Bytes"]| |Windows: Get filesystems|The `vfs.fs.get` key acquires raw information set about the file systems. Later to be extracted by preprocessing in dependent items.
|Zabbix agent (active)|vfs.fs.get| |Windows: Uptime|The system uptime expressed in the following format: "N days, hh:mm:ss".
|Zabbix agent (active)|system.uptime| |Windows: System local time|The local system time of the host.
|Zabbix agent (active)|system.localtime| |Windows: System name|The host name of the system.
|Zabbix agent (active)|system.hostname**Preprocessing**
Discard unchanged with heartbeat: `1d`
System description of the host.
|Zabbix agent (active)|system.uname**Preprocessing**
Discard unchanged with heartbeat: `1d`
The number of processes.
|Zabbix agent (active)|proc.num[]| |Windows: Number of threads|The number of threads used by all running processes.
|Zabbix agent (active)|perf_counter_en["\System\Threads"]| |Windows: Operating system architecture|The architecture of the operating system.
|Zabbix agent (active)|system.sw.arch**Preprocessing**
Discard unchanged with heartbeat: `1d`
**Preprocessing**
Discard unchanged with heartbeat: `1d`
Raw data of win32_networkadapter.
|Zabbix agent (active)|wmi.getall[root\cimv2,"select Name,Description,NetConnectionID,Speed,AdapterTypeId,NetConnectionStatus,GUID from win32_networkadapter where PhysicalAdapter=True and NetConnectionStatus>0"]**Preprocessing**
Discard unchanged with heartbeat: `1h`
For active agents, nodata() with agent.ping is used with {$AGENT.NODATA_TIMEOUT} as time threshold.
|`nodata(/Windows by Zabbix agent active/agent.ping,{$AGENT.NODATA_TIMEOUT})=1`|Average|**Manual close**: Yes| |Windows: Active checks are not available|Active checks are considered unavailable. Agent is not sending heartbeat for prolonged time.
|`min(/Windows by Zabbix agent active/zabbix[host,active_agent,available],{$AGENT.TIMEOUT})=2`|High|| |Windows: High CPU utilization|The CPU utilization is too high. The system might be slow to respond.
|`min(/Windows by Zabbix agent active/system.cpu.util,5m)>{$CPU.UTIL.CRIT}`|Warning|| |Windows: CPU interrupt time is too high|"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%.
The CPU privileged time in the last 5 minutes exceeds {$CPU.PRIV.CRIT.MAX}%.
|`min(/Windows by Zabbix agent active/perf_counter_en["\Processor Information(_total)\% Privileged Time"],5m)>{$CPU.PRIV.CRIT.MAX}`|Warning|**Depends on**: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 }.
|`min(/Windows by Zabbix agent active/perf_counter_en["\System\Processor Queue Length"],5m) - last(/Windows by Zabbix agent active/wmi.get[root/cimv2,"Select NumberOfLogicalProcessors from Win32_ComputerSystem"]) * 2 > {$CPU.QUEUE.CRIT.MAX}`|Warning|**Depends on**:The system is running out of free memory.
|`min(/Windows by Zabbix agent active/vm.memory.util,5m)>{$MEMORY.UTIL.MAX}`|Average|| |Windows: High swap space usage|This trigger is ignored, if there is no swap configured
|`max(/Windows by Zabbix agent active/system.swap.pfree,5m)<{$SWAP.PFREE.MIN.WARN} and last(/Windows by Zabbix agent active/system.swap.size[,total])>0`|Warning|**Depends on**:The Memory Free System Page Table Entries is less than {$MEM.PAGE_TABLE_CRIT.MIN} for 5 minutes. If the number is less than 5,000, there may well be a memory leak.
|`max(/Windows by Zabbix agent active/perf_counter_en["\Memory\Free System Page Table Entries"],5m)<{$MEM.PAGE_TABLE_CRIT.MIN}`|Warning|**Depends on**: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.
|`min(/Windows by Zabbix agent active/perf_counter_en["\Memory\Pages/sec"],5m)>{$MEM.PAGE_SEC.CRIT.MAX}`|Warning|**Depends on**:The device uptime is less than 10 minutes.
|`last(/Windows by Zabbix agent active/system.uptime)<10m`|Warning|**Manual close**: Yes| |Windows: System time is out of sync|The host's system time is different from Zabbix server time.
|`fuzzytime(/Windows by Zabbix agent active/system.localtime,{$SYSTEM.FUZZYTIME.MAX})=0`|Warning|**Manual close**: Yes| |Windows: System name has changed|The name of the system has changed. Acknowledge to close the problem manually.
|`change(/Windows by Zabbix agent active/system.hostname) and length(last(/Windows by Zabbix agent active/system.hostname))>0`|Info|**Manual close**: Yes| |Windows: 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.
|`change(/Windows by Zabbix agent active/system.sw.os) and length(last(/Windows by Zabbix agent active/system.sw.os))>0`|Info|**Manual close**: YesDiscovery of file systems of different types.
|Dependent item|vfs.fs.dependent.discovery| ### Item prototypes for Mounted filesystem discovery |Name|Description|Type|Key and additional info| |----|-----------|----|-----------------------| |{#FSLABEL}({#FSNAME}): Get filesystem data||Dependent item|vfs.fs.dependent[{#FSNAME},data]**Preprocessing**
JSON Path: `$.[?(@.fsname=='{#FSNAME}')].first()`
Used storage expressed in bytes.
|Dependent item|vfs.fs.dependent.size[{#FSNAME},used]**Preprocessing**
JSON Path: `$.bytes.used`
The total space expressed in bytes.
|Dependent item|vfs.fs.dependent.size[{#FSNAME},total]**Preprocessing**
JSON Path: `$.bytes.total`
Space utilization expressed in % for `{#FSNAME}`.
|Dependent item|vfs.fs.dependent.size[{#FSNAME},pused]**Preprocessing**
JSON Path: `$.bytes.pused`
Two conditions should match:
1. The first condition - utilization of the 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.
Two conditions should match:
1. The first condition - utilization of the space should be above `{$VFS.FS.PUSED.MAX.WARN:"{#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.
Discovery of installed physical disks.
|Zabbix agent (active)|perf_instance_en.discovery[PhysicalDisk]**Preprocessing**
Replace: `{#INSTANCE} -> {#DEVNAME}`
Rate of read operations on the disk.
|Zabbix agent (active)|perf_counter_en["\PhysicalDisk({#DEVNAME})\Disk Reads/sec",60]| |{#DEVNAME}: Disk write rate|Rate of write operations on the disk.
|Zabbix agent (active)|perf_counter_en["\PhysicalDisk({#DEVNAME})\Disk Writes/sec",60]| |{#DEVNAME}: Disk average queue size (avgqu-sz)|The current average disk queue; the number of requests outstanding on the disk while the performance data is being collected.
|Zabbix agent (active)|perf_counter_en["\PhysicalDisk({#DEVNAME})\Current Disk Queue Length",60]| |{#DEVNAME}: Disk utilization by idle time|This item is the percentage of elapsed time that the selected disk drive was busy servicing read or writes requests based on idle time.
|Zabbix agent (active)|perf_counter_en["\PhysicalDisk({#DEVNAME})\% Idle Time",60]**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.
|Zabbix agent (active)|perf_counter_en["\PhysicalDisk({#DEVNAME})\Avg. Disk sec/Read",60]| |{#DEVNAME}: Disk write request avg waiting time|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.
|Zabbix agent (active)|perf_counter_en["\PhysicalDisk({#DEVNAME})\Avg. Disk sec/Write",60]| |{#DEVNAME}: Average disk read queue length|Average disk read queue, the number of requests outstanding on the disk at the time the performance data is collected.
|Zabbix agent (active)|perf_counter_en["\PhysicalDisk({#DEVNAME})\Avg. Disk Read Queue Length",60]| |{#DEVNAME}: Average disk write queue length|Average disk write queue, the number of requests outstanding on the disk at the time the performance data is collected.
|Zabbix agent (active)|perf_counter_en["\PhysicalDisk({#DEVNAME})\Avg. Disk Write Queue Length",60]| ### Trigger prototypes for Physical disks discovery |Name|Description|Expression|Severity|Dependencies and additional info| |----|-----------|----------|--------|--------------------------------| |{#DEVNAME}: Disk is overloaded|The disk appears to be under heavy load.
|`min(/Windows by Zabbix agent active/perf_counter_en["\PhysicalDisk({#DEVNAME})\% Idle Time",60],15m)>{$VFS.DEV.UTIL.MAX.WARN}`|Warning|**Manual close**: YesThis trigger might indicate the disk {#DEVNAME} saturation.
|`min(/Windows by Zabbix agent active/perf_counter_en["\PhysicalDisk({#DEVNAME})\Avg. Disk sec/Read",60],15m) > {$VFS.DEV.READ.AWAIT.WARN:"{#DEVNAME}"}`|Warning|**Manual close**: Yes| |{#DEVNAME}: Disk write request responses are too high|This trigger might indicate the disk {#DEVNAME} saturation.
|`min(/Windows by Zabbix agent active/perf_counter_en["\PhysicalDisk({#DEVNAME})\Avg. Disk sec/Write",60],15m) > {$VFS.DEV.WRITE.AWAIT.WARN:"{#DEVNAME}"}`|Warning|**Manual close**: Yes| ### LLD rule Network interfaces discovery |Name|Description|Type|Key and additional info| |----|-----------|----|-----------------------| |Network interfaces discovery|Discovery of installed network interfaces.
|Dependent item|net.if.discovery**Preprocessing**
JavaScript: `The text is too long. Please see the template.`
Discard unchanged with heartbeat: `1h`
Incoming traffic on the network interface.
|Zabbix agent (active)|net.if.in["{#IFGUID}"]**Preprocessing**
Custom multiplier: `8`
Outgoing traffic on the network interface.
|Zabbix agent (active)|net.if.out["{#IFGUID}"]**Preprocessing**
Custom multiplier: `8`
The number of incoming packets dropped on the network interface.
|Zabbix agent (active)|net.if.in["{#IFGUID}",dropped]**Preprocessing**
The number of outgoing packets dropped on the network interface.
|Zabbix agent (active)|net.if.out["{#IFGUID}",dropped]**Preprocessing**
The number of incoming packets with errors on the network interface.
|Zabbix agent (active)|net.if.in["{#IFGUID}",errors]**Preprocessing**
The number of outgoing packets with errors on the network interface.
|Zabbix agent (active)|net.if.out["{#IFGUID}",errors]**Preprocessing**
Estimated bandwidth of the network interface if any.
|Dependent item|net.if.speed["{#IFGUID}"]**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.
|Dependent item|net.if.type["{#IFGUID}"]**Preprocessing**
JSON Path: `$[?(@.GUID == "{#IFGUID}")].AdapterTypeId.first()`
Discard unchanged with heartbeat: `1d`
The operational status of the network interface.
|Dependent item|net.if.status["{#IFGUID}"]**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.
|`(avg(/Windows by Zabbix agent active/net.if.in["{#IFGUID}"],15m)>({$IF.UTIL.MAX:"{#IFNAME}"}/100)*last(/Windows by Zabbix agent active/net.if.speed["{#IFGUID}"]) or avg(/Windows by Zabbix agent active/net.if.out["{#IFGUID}"],15m)>({$IF.UTIL.MAX:"{#IFNAME}"}/100)*last(/Windows by Zabbix agent active/net.if.speed["{#IFGUID}"])) and last(/Windows by Zabbix agent active/net.if.speed["{#IFGUID}"])>0`|Warning|**Manual close**: YesIt recovers when it is below 80% of the `{$IF.ERRORS.WARN:"{#IFNAME}"}` threshold.
|`min(/Windows by Zabbix agent active/net.if.in["{#IFGUID}",errors],5m)>{$IF.ERRORS.WARN:"{#IFNAME}"} or min(/Windows by Zabbix agent active/net.if.out["{#IFGUID}",errors],5m)>{$IF.ERRORS.WARN:"{#IFNAME}"}`|Warning|**Manual close**: YesThis Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Acknowledge to close the problem manually.
|`change(/Windows by Zabbix agent active/net.if.speed["{#IFGUID}"])<0 and last(/Windows by Zabbix agent active/net.if.speed["{#IFGUID}"])>0 and last(/Windows by Zabbix agent active/net.if.status["{#IFGUID}"])=2`|Info|**Manual close**: YesThis 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.
|Zabbix agent (active)|service.discovery| ### Item prototypes for Windows services discovery |Name|Description|Type|Key and additional info| |----|-----------|----|-----------------------| |State of service "{#SERVICE.NAME}" ({#SERVICE.DISPLAYNAME})||Zabbix agent (active)|service.info["{#SERVICE.NAME}",state]| ### Trigger prototypes for Windows services discovery |Name|Description|Expression|Severity|Dependencies and additional info| |----|-----------|----------|--------|--------------------------------| |"{#SERVICE.NAME}" ({#SERVICE.DISPLAYNAME}) is not running|The service has a state other than "Running" for the last three times.
|`min(/Windows by Zabbix agent active/service.info["{#SERVICE.NAME}",state],#3)<>0`|Average|| ## Feedback Please report any issues with the template at [`https://support.zabbix.com`](https://support.zabbix.com) You can also provide feedback, discuss the template, or ask for help at [`ZABBIX forums`](https://www.zabbix.com/forum/zabbix-suggestions-and-feedback)