После установки ZABBIX и его настройки пришло время приступить к созданию шаблонов мониторинга. По умолчанию в системе доступно множество готовых к использованию шаблонов и в большинстве случаев они вполне способны решать многие задачи по наблюдению и выявлению неисправностей, а потому вам остается лишь добавить необходимые для наблюдения узлы или устройства, настроить хотя бы небольшую иерархию и логически сгруппировать объекты мониторинга. Интерфейс ZABBIX в принципе позволяет без чтения документации самостоятельно разобраться в настройках, но все же новичка будут сильно раздражать неочевидные моменты и огрехи в разработке интерфейса — надо признать, что он получился далеко не самым удобным, а многие основные элементы управления выглядят просто «слепо» и неопытный администратор не сразу обратит на них внимание. Однако все же стоит сказать большое спасибо разработчикам продукта хотя бы за то, что этот интерфейс все же есть и подавляющее большинство задач администрирования и настройки можно выполнить именно из него.
Если вам интересна тематика ZABBIX, рекомендую обратиться к основной статье — Система мониторинга ZABBIX, в ней вы найдете дополнительную информацию.
Шаблоны ZABBIX
Дефолтные шаблоны ZABBIX покрывают достаточно большую область мониторинга, начиная от unix- и windows- систем, заканчивая сетевыми устройствами. Тем не менее перед системными администраторами часто встает задача ручного допиливания шаблонов, а иногда и вообще создания собственных с нуля. В этом вам помогут мои статьи, ну и конечно же официальная документация.
Найти информацию о шаблонах мониторинга в моем блоге вы сможете в следующих статьях:
Мониторинг MySQL в ZABBIX — тюнинг СУБД всегда был важной задачей и без отслеживания ключевых показателей вы вряд ли добьетесь в этом деле успеха;
Мониторинг Apache в ZABBIX — нельзя забывать про отслеживание показателей одного из самых популярных веб-сервисов;
Мониторинг дисков ZABBIX — дефолтные шаблоны не предоставляют возможности для широкого мониторинга дисков unix-систем, эта статья призвана устранить этот недочет;
Шаблоны Windows в ZABBIX — мониторинг Windows — это отдельная тематика, а потому я посветил ей целую статью и вероятнее всего на этом дело не кончится.
Тем не менее «затачивание» шаблонов под свои нужды представляет из себя далеко не самую простую задачу и сделать это можно не за один раз и не за короткий временной промежуток. Поскольку большинство системных администраторов вообще не используют системы мониторинга, следовательно каких-то больших сообществ и «клубов по интересам» касательно этих систем в интернете очень мало, либо нет вообще. Все это делает малодоступным свободное перенимание опыта со стороны новичков от их «видавших многое» коллег. И это особо актуально по отношению лучших практик мониторинга критически важных элементов серверов, сетевых устройств. Все это делает достаточно ценным ваши собственные шаблоны мониторинга, которые вы создавали, расширяли и совершенствовали на протяжении многих лет практики системного администрирования. Если кто-то пока не понимает о чем идет речь, то поясню: если единственная цель мониторинга сервера — понять включен он или выключен, то тут все просто и задача упирается во всего лишь один триггер, отвечающий за уведомление в случае отсутствия от сервера признаков жизни; однако если вы ставите целью понимание насколько аппаратное обеспечение сервера отвечает требованиям производительности со стороны ПО и когда может потребоваться сделать апгрейд, либо вашей задачей является тюнинг СУБД и выявление узких мест в работе системы, а может быть предмет вашего мониторинга — сложная система, состоящая из массы связанных друг с другом узлов с множеством служб (например, кластер), то в этих случаях вам придется самостоятельно «допиливать» шаблоны мониторинга под себя и никто с вами ничем не поделится и по-простому проскочить не получится.
Вот и у меня за годы использования ZABBIX накопились некоторые знания и навыки в администрировании этой системы и цель статьи этими знаниями поделиться. По мере изменений я буду выкладывать свои шаблоны ZABBIX и при необходимости их можно будет скачать. Пока основным и наиболее сложным моментом является анализ счетчиков производительности Windows, ведь их надо анализировать в комплексе и эту задачу я решаю следующим образом: по возможности в каждом ключе данных пишу комментарии как этот счетчик можно использовать и с какими другими показателями его надо анализировать. Что-то из этого — личный опыт, а что-то найдено в сети и источники я тоже буду стараться выкладывать.
Источник
Zabbix + Linux
Linux
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991, by Linus Torvalds. Linux is typically packaged in a Linux distribution.
Available solutions
Also available for: 5.0
Linux CPU by Zabbix agent
Overview
For Zabbix version: 5.4 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
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
Template links
There are no template links in this template.
Discovery rules
Name
Description
Type
Key and additional info
Mounted filesystem discovery
Discovery of file systems of different types.
ZABBIX_PASSIVE
vfs.fs.discovery
Filter:
Items collected
Group
Name
Description
Type
Key and additional info
Filesystems
<#FSNAME>: Used space
Used storage in Bytes
ZABBIX_PASSIVE
vfs.fs.size[<#FSNAME>,used]
Filesystems
<#FSNAME>: Total space
Total space in Bytes
ZABBIX_PASSIVE
vfs.fs.size[<#FSNAME>,total]
Filesystems
<#FSNAME>: Space utilization
Space utilization in % for
ZABBIX_PASSIVE
vfs.fs.size[<#FSNAME>,pused]
Filesystems
<#FSNAME>: Free inodes in %
ZABBIX_PASSIVE
vfs.fs.inode[<#FSNAME>,pfree]
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
<#FSNAME>: Disk space is critically low (used > <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>%)
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 5G.
— The disk will be full in less than 24 hours.
,pused].last()>><$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«> and ((,total].last()>-,used].last()>)
AVERAGE
Manual close: YES
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 10G.
— The disk will be full in less than 24 hours.
,pused].last()>><$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«> and ((,total].last()>-,used].last()>)
WARNING
Manual close: YES
Depends on:
<#FSNAME>: Running out of free inodes (free ,pfree].min(5m)>
AVERAGE
<#FSNAME>: Running out of free inodes (free ,pfree].min(5m)>
WARNING
Depends on:
— <#FSNAME>: Running out of free inodes (free 20M
This macro is used as a threshold in memory utilization trigger.
Template links
There are no template links in this template.
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Memory
Memory utilization
Memory used percentage is calculated as (100-pavailable)
DEPENDENT
vm.memory.utilization
Preprocessing:
— JAVASCRIPT: return (100-value);
ZABBIX_PASSIVE
vm.memory.size[pavailable]
Memory
Total memory
Total memory in Bytes
ZABBIX_PASSIVE
vm.memory.size[total]
Memory
Available memory
Available memory, in Linux, available = free + buffers + cache. On other platforms calculation may vary. See also: https://www.zabbix.com/documentation/5.4/manual/appendix/items/vm.memory.size_params
ZABBIX_PASSIVE
vm.memory.size[available]
Memory
Total swap space
The total space of swap volume/file in bytes.
ZABBIX_PASSIVE
system.swap.size[,total]
Memory
Free swap space
The free space of swap volume/file in bytes.
ZABBIX_PASSIVE
system.swap.size[,free]
Memory
Free swap space in %
The free space of swap volume/file in percent.
ZABBIX_PASSIVE
system.swap.size[,pfree]
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
The system is running out of free memory.
Depends on:
— Lack of available memory ( 0
AVERAGE
High swap space usage (less than <$SWAP.PFREE.MIN.WARN>% free)
This trigger is ignored, if there is no swap configured
Depends on:
— High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
— Lack of available memory ( .+
This macro is used in block devices discovery. Can be overridden on the host or linked template level
Disk read average response time (in ms) before the trigger would fire
Disk write average response time (in ms) before the trigger would fire
Template links
There are no template links in this template.
Discovery rules
Name
Description
Type
Key and additional info
Block devices discovery
ZABBIX_PASSIVE
vfs.dev.discovery
Preprocessing:
Filter:
— A: <#DEVTYPE>MATCHES_REGEX disk
Items collected
Group
Name
Description
Type
Key and additional info
Storage
<#DEVNAME>: Disk read rate
r/s. The number (after merges) of read requests completed per second for the device.
DEPENDENT
vfs.dev.read.rate[<#DEVNAME>]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk write rate
w/s. The number (after merges) of write requests completed per second for the device.
DEPENDENT
vfs.dev.write.rate[<#DEVNAME>]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk read request avg waiting time (r_await)
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.
<#DEVNAME>: Disk write request avg waiting time (w_await)
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.
Rate of total read time counter. Used in r_await calculation
DEPENDENT
vfs.dev.read.time.rate[<#DEVNAME>]
Preprocessing:
Zabbix_raw_items
<#DEVNAME>: Disk write time (rate)
Rate of total write time counter. Used in w_await calculation
DEPENDENT
vfs.dev.write.time.rate[<#DEVNAME>]
Preprocessing:
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
<#DEVNAME>: Disk read/write request responses are too high (read > <$VFS.DEV.READ.AWAIT.WARN:"<#DEVNAME>«> ms for 15m or write > <$VFS.DEV.WRITE.AWAIT.WARN:"<#DEVNAME>«> ms for 15m)
This trigger might indicate disk <#DEVNAME>saturation.
Manual close: YES
Feedback
Please report any issues with the template at https://support.zabbix.com
Linux network interfaces by Zabbix agent
Overview
For Zabbix version: 5.4 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Filter out loopbacks, nulls, docker veth links and docker0 bridge by default
Interface <#IFNAME>: High error rate (> <$IF.ERRORS.WARN:"<#IFNAME>«> for 5m)
Recovers when below 80% of <$IF.ERRORS.WARN:"<#IFNAME>«> threshold
«,errors].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«> or «,errors].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«>
«,errors].max(5m)>
WARNING
Manual close: YES
Depends on:
— Interface <#IFNAME>: Link down
This trigger expression works as follows:
1. Can be triggered if operations status is down.
2. <$IFCONTROL:"<#IFNAME>«>=1 — user can redefine Context macro to value — 0. That marks this interface as not important. No new trigger will be fired if this interface is down.
3. =1) — trigger fires only if operational status was up(1) sometime before. (So, do not fire ‘ethernal off’ interfaces.)
WARNING: if closed manually — won’t fire again on next poll, because of .diff.
<$IFCONTROL:"<#IFNAME>«>=1 and (/operstate»].last()>=2 and /operstate»].diff()>=1)
/operstate»].last()><>2 or <$IFCONTROL:"<#IFNAME>«>=0
AVERAGE
Manual close: YES
Interface <#IFNAME>: Ethernet has changed to lower speed than it was before
This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close.
/type»].change()> 0 and (/type»].last()>=6 or /type»].last()>=1) and (/operstate»].last()><>2)
(/type»].change()>>0 and /type»].prev()>>0) or (/operstate»].last()>=2)
INFO
Manual close: YES
Depends on:
— Interface <#IFNAME>: Link down
Feedback
Please report any issues with the template at https://support.zabbix.com
Known Issues
Description: High interface utilization trigger is removed since currently it is not possible to retrieve interface speed to determine the max bandwidth.
Linux generic by Zabbix agent
Overview
For Zabbix version: 5.4 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Template links
There are no template links in this template.
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
General
System boot time
ZABBIX_PASSIVE
system.boottime
Preprocessing:
System local time of the host.
ZABBIX_PASSIVE
system.localtime
General
System name
System host name.
ZABBIX_PASSIVE
system.hostname
Preprocessing:
The information as normally returned by ‘uname -a’.
ZABBIX_PASSIVE
system.uname
Preprocessing:
General
Number of logged in users
Number of users who are currently logged in.
ZABBIX_PASSIVE
system.users.num
General
Maximum number of open file descriptors
It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf.
ZABBIX_PASSIVE
kernel.maxfiles
Preprocessing:
General
Maximum number of processes
It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf.
ZABBIX_PASSIVE
kernel.maxproc
Preprocessing:
ZABBIX_PASSIVE
proc.num
General
Number of running processes
ZABBIX_PASSIVE
proc.num[,,run]
Inventory
Operating system
ZABBIX_PASSIVE
system.sw.os
Preprocessing:
Inventory
Operating system architecture
Operating system architecture of the host.
ZABBIX_PASSIVE
system.sw.arch
Preprocessing:
ZABBIX_PASSIVE
system.sw.packages
Preprocessing:
Security
Checksum of /etc/passwd
ZABBIX_PASSIVE
vfs.file.cksum[/etc/passwd]
Preprocessing:
System uptime in ‘N days, hh:mm:ss’ format.
ZABBIX_PASSIVE
system.uptime
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
System time is out of sync (diff with Zabbix server > <$SYSTEM.FUZZYTIME.MAX>s)
The host system time is different from the Zabbix server time.
Manual close: YES
System name has changed (new name: )
System name has changed. Ack to close.
Manual close: YES
Configured max number of open filedescriptors is too low (
INFO
Configured max number of processes is too low (
INFO
Depends on:
— Getting closer to process limit (over 80% used)
Getting closer to process limit (over 80% used)
/*100>80
WARNING
Operating system description has changed
Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.
Manual close: YES
Depends on:
— System name has changed (new name: )
Manual close: YES
Depends on:
— Operating system description has changed
— System name has changed (new name: )
has been restarted (uptime
WARNING
Manual close: YES
Feedback
Please report any issues with the template at https://support.zabbix.com
Linux by Zabbix agent
Overview
For Zabbix version: 5.4 and higher New official Linux template. Requires agent of Zabbix 3.0.14, 3.4.5 and 4.0.0 or newer.
Setup
Install Zabbix agent on Linux OS according to Zabbix documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Template links
Name
Linux CPU by Zabbix agent
Linux block devices by Zabbix agent
Linux filesystems by Zabbix agent
Linux generic by Zabbix agent
Linux memory by Zabbix agent
Linux network interfaces by Zabbix agent
Zabbix agent
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide a feedback, discuss the template or ask for help with it at ZABBIX forums.
Known Issues
Description: Network discovery. Zabbix agent as of 4.2 doesn’t support items such as net.if.status, net.if.speed.
Also available for: 5.4
Linux CPU by Zabbix agent
Overview
For Zabbix version: 5.0 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
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
Template links
There are no template links in this template.
Discovery rules
Name
Description
Type
Key and additional info
Mounted filesystem discovery
Discovery of file systems of different types.
ZABBIX_PASSIVE
vfs.fs.discovery
Filter:
Items collected
Group
Name
Description
Type
Key and additional info
Filesystems
<#FSNAME>: Used space
Used storage in Bytes
ZABBIX_PASSIVE
vfs.fs.size[<#FSNAME>,used]
Filesystems
<#FSNAME>: Total space
Total space in Bytes
ZABBIX_PASSIVE
vfs.fs.size[<#FSNAME>,total]
Filesystems
<#FSNAME>: Space utilization
Space utilization in % for
ZABBIX_PASSIVE
vfs.fs.size[<#FSNAME>,pused]
Filesystems
<#FSNAME>: Free inodes in %
ZABBIX_PASSIVE
vfs.fs.inode[<#FSNAME>,pfree]
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
<#FSNAME>: Disk space is critically low (used > <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>%)
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 5G.
— The disk will be full in less than 24 hours.
,pused].last()>><$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«> and ((,total].last()>-,used].last()>)
AVERAGE
Manual close: YES
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 10G.
— The disk will be full in less than 24 hours.
,pused].last()>><$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«> and ((,total].last()>-,used].last()>)
WARNING
Manual close: YES
Depends on:
<#FSNAME>: Running out of free inodes (free ,pfree].min(5m)>
AVERAGE
<#FSNAME>: Running out of free inodes (free ,pfree].min(5m)>
WARNING
Depends on:
— <#FSNAME>: Running out of free inodes (free 20M
This macro is used as a threshold in memory utilization trigger.
Template links
There are no template links in this template.
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Memory
Memory utilization
Memory used percentage is calculated as (100-pavailable)
DEPENDENT
vm.memory.utilization
Preprocessing:
— JAVASCRIPT: return (100-value);
ZABBIX_PASSIVE
vm.memory.size[pavailable]
Memory
Total memory
Total memory in Bytes
ZABBIX_PASSIVE
vm.memory.size[total]
Memory
Available memory
Available memory, in Linux, available = free + buffers + cache. On other platforms calculation may vary. See also: https://www.zabbix.com/documentation/5.0/manual/appendix/items/vm.memory.size_params
ZABBIX_PASSIVE
vm.memory.size[available]
Memory
Total swap space
The total space of swap volume/file in bytes.
ZABBIX_PASSIVE
system.swap.size[,total]
Memory
Free swap space
The free space of swap volume/file in bytes.
ZABBIX_PASSIVE
system.swap.size[,free]
Memory
Free swap space in %
The free space of swap volume/file in percent.
ZABBIX_PASSIVE
system.swap.size[,pfree]
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
The system is running out of free memory.
Depends on:
— Lack of available memory ( 0
AVERAGE
High swap space usage (less than <$SWAP.PFREE.MIN.WARN>% free)
This trigger is ignored, if there is no swap configured
Depends on:
— High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
— Lack of available memory ( .+
This macro is used in block devices discovery. Can be overridden on the host or linked template level
Disk read average response time (in ms) before the trigger would fire
Disk write average response time (in ms) before the trigger would fire
Template links
There are no template links in this template.
Discovery rules
Name
Description
Type
Key and additional info
Block devices discovery
ZABBIX_PASSIVE
vfs.dev.discovery
Preprocessing:
Filter:
— A: <#DEVTYPE>MATCHES_REGEX disk
Items collected
Group
Name
Description
Type
Key and additional info
Storage
<#DEVNAME>: Disk read rate
r/s. The number (after merges) of read requests completed per second for the device.
DEPENDENT
vfs.dev.read.rate[<#DEVNAME>]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk write rate
w/s. The number (after merges) of write requests completed per second for the device.
DEPENDENT
vfs.dev.write.rate[<#DEVNAME>]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk read request avg waiting time (r_await)
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.
<#DEVNAME>: Disk write request avg waiting time (w_await)
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.
Rate of total read time counter. Used in r_await calculation
DEPENDENT
vfs.dev.read.time.rate[<#DEVNAME>]
Preprocessing:
Zabbix_raw_items
<#DEVNAME>: Disk write time (rate)
Rate of total write time counter. Used in w_await calculation
DEPENDENT
vfs.dev.write.time.rate[<#DEVNAME>]
Preprocessing:
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
<#DEVNAME>: Disk read/write request responses are too high (read > <$VFS.DEV.READ.AWAIT.WARN:"<#DEVNAME>«> ms for 15m or write > <$VFS.DEV.WRITE.AWAIT.WARN:"<#DEVNAME>«> ms for 15m)
This trigger might indicate disk <#DEVNAME>saturation.
Manual close: YES
Feedback
Please report any issues with the template at https://support.zabbix.com
Linux network interfaces by Zabbix agent
Overview
For Zabbix version: 5.0 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Filter out loopbacks, nulls, docker veth links and docker0 bridge by default
Interface <#IFNAME>: High error rate (> <$IF.ERRORS.WARN:"<#IFNAME>«> for 5m)
Recovers when below 80% of <$IF.ERRORS.WARN:"<#IFNAME>«> threshold
«,errors].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«> or «,errors].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«>
«,errors].max(5m)>
WARNING
Manual close: YES
Depends on:
— Interface <#IFNAME>: Link down
This trigger expression works as follows:
1. Can be triggered if operations status is down.
2. <$IFCONTROL:"<#IFNAME>«>=1 — user can redefine Context macro to value — 0. That marks this interface as not important. No new trigger will be fired if this interface is down.
3. =1) — trigger fires only if operational status was up(1) sometime before. (So, do not fire ‘ethernal off’ interfaces.)
WARNING: if closed manually — won’t fire again on next poll, because of .diff.
<$IFCONTROL:"<#IFNAME>«>=1 and (/operstate»].last()>=2 and /operstate»].diff()>=1)
/operstate»].last()><>2 or <$IFCONTROL:"<#IFNAME>«>=0
AVERAGE
Manual close: YES
Interface <#IFNAME>: Ethernet has changed to lower speed than it was before
This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close.
/type»].change()> 0 and (/type»].last()>=6 or /type»].last()>=1) and (/operstate»].last()><>2)
(/type»].change()>>0 and /type»].prev()>>0) or (/operstate»].last()>=2)
INFO
Manual close: YES
Depends on:
— Interface <#IFNAME>: Link down
Feedback
Please report any issues with the template at https://support.zabbix.com
Known Issues
Description: High interface utilization trigger is removed since currently it is not possible to retrieve interface speed to determine the max bandwidth.
Linux generic by Zabbix agent
Overview
For Zabbix version: 5.0 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Template links
There are no template links in this template.
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
General
System boot time
ZABBIX_PASSIVE
system.boottime
Preprocessing:
System local time of the host.
ZABBIX_PASSIVE
system.localtime
General
System name
System host name.
ZABBIX_PASSIVE
system.hostname
Preprocessing:
The information as normally returned by ‘uname -a’.
ZABBIX_PASSIVE
system.uname
Preprocessing:
General
Number of logged in users
Number of users who are currently logged in.
ZABBIX_PASSIVE
system.users.num
General
Maximum number of open file descriptors
It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf.
ZABBIX_PASSIVE
kernel.maxfiles
Preprocessing:
General
Maximum number of processes
It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf.
ZABBIX_PASSIVE
kernel.maxproc
Preprocessing:
ZABBIX_PASSIVE
proc.num
General
Number of running processes
ZABBIX_PASSIVE
proc.num[,,run]
Inventory
Operating system
ZABBIX_PASSIVE
system.sw.os
Preprocessing:
Inventory
Operating system architecture
Operating system architecture of the host.
ZABBIX_PASSIVE
system.sw.arch
Preprocessing:
ZABBIX_PASSIVE
system.sw.packages
Preprocessing:
Security
Checksum of /etc/passwd
ZABBIX_PASSIVE
vfs.file.cksum[/etc/passwd]
Preprocessing:
System uptime in ‘N days, hh:mm:ss’ format.
ZABBIX_PASSIVE
system.uptime
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
System time is out of sync (diff with Zabbix server > <$SYSTEM.FUZZYTIME.MAX>s)
The host system time is different from the Zabbix server time.
Manual close: YES
System name has changed (new name: )
System name has changed. Ack to close.
Manual close: YES
Configured max number of open filedescriptors is too low (
INFO
Configured max number of processes is too low (
INFO
Depends on:
— Getting closer to process limit (over 80% used)
Getting closer to process limit (over 80% used)
/*100>80
WARNING
Operating system description has changed
Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.
Manual close: YES
Depends on:
— System name has changed (new name: )
Manual close: YES
Depends on:
— Operating system description has changed
— System name has changed (new name: )
has been restarted (uptime
WARNING
Manual close: YES
Feedback
Please report any issues with the template at https://support.zabbix.com
Linux by Zabbix agent
Overview
For Zabbix version: 5.0 and higher New official Linux template. Requires agent of Zabbix 3.0.14, 3.4.5 and 4.0.0 or newer.
Setup
Install Zabbix agent on Linux OS according to Zabbix documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Template links
Name
Linux CPU by Zabbix agent
Linux block devices by Zabbix agent
Linux filesystems by Zabbix agent
Linux generic by Zabbix agent
Linux memory by Zabbix agent
Linux network interfaces by Zabbix agent
Zabbix agent
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide a feedback, discuss the template or ask for help with it at ZABBIX forums.
Known Issues
Description: Network discovery. Zabbix agent as of 4.2 doesn’t support items such as net.if.status, net.if.speed.
Also available for: 5.0
Linux CPU by Zabbix agent active
Overview
For Zabbix version: 5.4 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
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
Template links
There are no template links in this template.
Discovery rules
Name
Description
Type
Key and additional info
Mounted filesystem discovery
Discovery of file systems of different types.
ZABBIX_ACTIVE
vfs.fs.discovery
Filter:
Items collected
Group
Name
Description
Type
Key and additional info
Filesystems
<#FSNAME>: Used space
Used storage in Bytes
ZABBIX_ACTIVE
vfs.fs.size[<#FSNAME>,used]
Filesystems
<#FSNAME>: Total space
Total space in Bytes
ZABBIX_ACTIVE
vfs.fs.size[<#FSNAME>,total]
Filesystems
<#FSNAME>: Space utilization
Space utilization in % for
ZABBIX_ACTIVE
vfs.fs.size[<#FSNAME>,pused]
Filesystems
<#FSNAME>: Free inodes in %
ZABBIX_ACTIVE
vfs.fs.inode[<#FSNAME>,pfree]
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
<#FSNAME>: Disk space is critically low (used > <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>%)
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 5G.
— The disk will be full in less than 24 hours.
,pused].last()>><$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«> and ((,total].last()>-,used].last()>)
AVERAGE
Manual close: YES
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 10G.
— The disk will be full in less than 24 hours.
,pused].last()>><$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«> and ((,total].last()>-,used].last()>)
WARNING
Manual close: YES
Depends on:
<#FSNAME>: Running out of free inodes (free ,pfree].min(5m)>
AVERAGE
<#FSNAME>: Running out of free inodes (free ,pfree].min(5m)>
WARNING
Depends on:
— <#FSNAME>: Running out of free inodes (free 20M
This macro is used as a threshold in memory utilization trigger.
Template links
There are no template links in this template.
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Memory
Memory utilization
Memory used percentage is calculated as (100-pavailable)
DEPENDENT
vm.memory.utilization
Preprocessing:
— JAVASCRIPT: return (100-value);
ZABBIX_ACTIVE
vm.memory.size[pavailable]
Memory
Total memory
Total memory in Bytes
ZABBIX_ACTIVE
vm.memory.size[total]
Memory
Available memory
Available memory, in Linux, available = free + buffers + cache. On other platforms calculation may vary. See also: https://www.zabbix.com/documentation/5.4/manual/appendix/items/vm.memory.size_params
ZABBIX_ACTIVE
vm.memory.size[available]
Memory
Total swap space
The total space of swap volume/file in bytes.
ZABBIX_ACTIVE
system.swap.size[,total]
Memory
Free swap space
The free space of swap volume/file in bytes.
ZABBIX_ACTIVE
system.swap.size[,free]
Memory
Free swap space in %
The free space of swap volume/file in percent.
ZABBIX_ACTIVE
system.swap.size[,pfree]
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
The system is running out of free memory.
Depends on:
— Lack of available memory ( 0
AVERAGE
High swap space usage (less than <$SWAP.PFREE.MIN.WARN>% free)
This trigger is ignored, if there is no swap configured
Depends on:
— High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
— Lack of available memory ( .+
This macro is used in block devices discovery. Can be overridden on the host or linked template level
Disk read average response time (in ms) before the trigger would fire
Disk write average response time (in ms) before the trigger would fire
Template links
There are no template links in this template.
Discovery rules
Name
Description
Type
Key and additional info
Block devices discovery
ZABBIX_ACTIVE
vfs.dev.discovery
Preprocessing:
Filter:
— A: <#DEVTYPE>MATCHES_REGEX disk
Items collected
Group
Name
Description
Type
Key and additional info
Storage
<#DEVNAME>: Disk read rate
r/s. The number (after merges) of read requests completed per second for the device.
DEPENDENT
vfs.dev.read.rate[<#DEVNAME>]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk write rate
w/s. The number (after merges) of write requests completed per second for the device.
DEPENDENT
vfs.dev.write.rate[<#DEVNAME>]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk read request avg waiting time (r_await)
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.
<#DEVNAME>: Disk write request avg waiting time (w_await)
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.
Rate of total read time counter. Used in r_await calculation
DEPENDENT
vfs.dev.read.time.rate[<#DEVNAME>]
Preprocessing:
Zabbix_raw_items
<#DEVNAME>: Disk write time (rate)
Rate of total write time counter. Used in w_await calculation
DEPENDENT
vfs.dev.write.time.rate[<#DEVNAME>]
Preprocessing:
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
<#DEVNAME>: Disk read/write request responses are too high (read > <$VFS.DEV.READ.AWAIT.WARN:"<#DEVNAME>«> ms for 15m or write > <$VFS.DEV.WRITE.AWAIT.WARN:"<#DEVNAME>«> ms for 15m)
This trigger might indicate disk <#DEVNAME>saturation.
Manual close: YES
Feedback
Please report any issues with the template at https://support.zabbix.com
Linux network interfaces by Zabbix agent active
Overview
For Zabbix version: 5.4 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Filter out loopbacks, nulls, docker veth links and docker0 bridge by default
Interface <#IFNAME>: High error rate (> <$IF.ERRORS.WARN:"<#IFNAME>«> for 5m)
Recovers when below 80% of <$IF.ERRORS.WARN:"<#IFNAME>«> threshold
«,errors].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«> or «,errors].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«>
«,errors].max(5m)>
WARNING
Manual close: YES
Depends on:
— Interface <#IFNAME>: Link down
This trigger expression works as follows:
1. Can be triggered if operations status is down.
2. <$IFCONTROL:"<#IFNAME>«>=1 — user can redefine Context macro to value — 0. That marks this interface as not important. No new trigger will be fired if this interface is down.
3. =1) — trigger fires only if operational status was up(1) sometime before. (So, do not fire ‘ethernal off’ interfaces.)
WARNING: if closed manually — won’t fire again on next poll, because of .diff.
<$IFCONTROL:"<#IFNAME>«>=1 and (/operstate»].last()>=2 and /operstate»].diff()>=1)
/operstate»].last()><>2 or <$IFCONTROL:"<#IFNAME>«>=0
AVERAGE
Manual close: YES
Interface <#IFNAME>: Ethernet has changed to lower speed than it was before
This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close.
/type»].change()> 0 and (/type»].last()>=6 or /type»].last()>=1) and (/operstate»].last()><>2)
(/type»].change()>>0 and /type»].prev()>>0) or (/operstate»].last()>=2)
INFO
Manual close: YES
Depends on:
— Interface <#IFNAME>: Link down
Feedback
Please report any issues with the template at https://support.zabbix.com
Known Issues
Description: High interface utilization trigger is removed since currently it is not possible to retrieve interface speed to determine the max bandwidth.
Linux generic by Zabbix agent active
Overview
For Zabbix version: 5.4 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Template links
There are no template links in this template.
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
General
System boot time
ZABBIX_ACTIVE
system.boottime
Preprocessing:
System local time of the host.
ZABBIX_ACTIVE
system.localtime
General
System name
System host name.
ZABBIX_ACTIVE
system.hostname
Preprocessing:
The information as normally returned by ‘uname -a’.
ZABBIX_ACTIVE
system.uname
Preprocessing:
General
Number of logged in users
Number of users who are currently logged in.
ZABBIX_ACTIVE
system.users.num
General
Maximum number of open file descriptors
It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf.
ZABBIX_ACTIVE
kernel.maxfiles
Preprocessing:
General
Maximum number of processes
It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf.
ZABBIX_ACTIVE
kernel.maxproc
Preprocessing:
ZABBIX_ACTIVE
proc.num
General
Number of running processes
ZABBIX_ACTIVE
proc.num[,,run]
Inventory
Operating system
ZABBIX_ACTIVE
system.sw.os
Preprocessing:
Inventory
Operating system architecture
Operating system architecture of the host.
ZABBIX_ACTIVE
system.sw.arch
Preprocessing:
ZABBIX_ACTIVE
system.sw.packages
Preprocessing:
Security
Checksum of /etc/passwd
ZABBIX_ACTIVE
vfs.file.cksum[/etc/passwd]
Preprocessing:
System uptime in ‘N days, hh:mm:ss’ format.
ZABBIX_ACTIVE
system.uptime
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
System time is out of sync (diff with Zabbix server > <$SYSTEM.FUZZYTIME.MAX>s)
The host system time is different from the Zabbix server time.
Manual close: YES
System name has changed (new name: )
System name has changed. Ack to close.
Manual close: YES
Configured max number of open filedescriptors is too low (
INFO
Configured max number of processes is too low (
INFO
Depends on:
— Getting closer to process limit (over 80% used)
Getting closer to process limit (over 80% used)
/*100>80
WARNING
Operating system description has changed
Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.
Manual close: YES
Depends on:
— System name has changed (new name: )
Manual close: YES
Depends on:
— Operating system description has changed
— System name has changed (new name: )
has been restarted (uptime
WARNING
Manual close: YES
Feedback
Please report any issues with the template at https://support.zabbix.com
Linux by Zabbix agent active
Overview
For Zabbix version: 5.4 and higher New official Linux template. Requires agent of Zabbix 3.0.14, 3.4.5 and 4.0.0 or newer.
Setup
Install Zabbix agent on Linux OS according to Zabbix documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Template links
Name
Linux CPU by Zabbix agent active
Linux block devices by Zabbix agent active
Linux filesystems by Zabbix agent active
Linux generic by Zabbix agent active
Linux memory by Zabbix agent active
Linux network interfaces by Zabbix agent active
Zabbix agent
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide a feedback, discuss the template or ask for help with it at ZABBIX forums.
Known Issues
Description: Network discovery. Zabbix agent as of 4.2 doesn’t support items such as net.if.status, net.if.speed.
Also available for: 5.4
Linux CPU by Zabbix agent active
Overview
For Zabbix version: 5.0 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
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
Template links
There are no template links in this template.
Discovery rules
Name
Description
Type
Key and additional info
Mounted filesystem discovery
Discovery of file systems of different types.
ZABBIX_ACTIVE
vfs.fs.discovery
Filter:
Items collected
Group
Name
Description
Type
Key and additional info
Filesystems
<#FSNAME>: Used space
Used storage in Bytes
ZABBIX_ACTIVE
vfs.fs.size[<#FSNAME>,used]
Filesystems
<#FSNAME>: Total space
Total space in Bytes
ZABBIX_ACTIVE
vfs.fs.size[<#FSNAME>,total]
Filesystems
<#FSNAME>: Space utilization
Space utilization in % for
ZABBIX_ACTIVE
vfs.fs.size[<#FSNAME>,pused]
Filesystems
<#FSNAME>: Free inodes in %
ZABBIX_ACTIVE
vfs.fs.inode[<#FSNAME>,pfree]
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
<#FSNAME>: Disk space is critically low (used > <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>%)
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 5G.
— The disk will be full in less than 24 hours.
,pused].last()>><$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«> and ((,total].last()>-,used].last()>)
AVERAGE
Manual close: YES
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 10G.
— The disk will be full in less than 24 hours.
,pused].last()>><$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«> and ((,total].last()>-,used].last()>)
WARNING
Manual close: YES
Depends on:
<#FSNAME>: Running out of free inodes (free ,pfree].min(5m)>
AVERAGE
<#FSNAME>: Running out of free inodes (free ,pfree].min(5m)>
WARNING
Depends on:
— <#FSNAME>: Running out of free inodes (free 20M
This macro is used as a threshold in memory utilization trigger.
Template links
There are no template links in this template.
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Memory
Memory utilization
Memory used percentage is calculated as (100-pavailable)
DEPENDENT
vm.memory.utilization
Preprocessing:
— JAVASCRIPT: return (100-value);
ZABBIX_ACTIVE
vm.memory.size[pavailable]
Memory
Total memory
Total memory in Bytes
ZABBIX_ACTIVE
vm.memory.size[total]
Memory
Available memory
Available memory, in Linux, available = free + buffers + cache. On other platforms calculation may vary. See also: https://www.zabbix.com/documentation/5.0/manual/appendix/items/vm.memory.size_params
ZABBIX_ACTIVE
vm.memory.size[available]
Memory
Total swap space
The total space of swap volume/file in bytes.
ZABBIX_ACTIVE
system.swap.size[,total]
Memory
Free swap space
The free space of swap volume/file in bytes.
ZABBIX_ACTIVE
system.swap.size[,free]
Memory
Free swap space in %
The free space of swap volume/file in percent.
ZABBIX_ACTIVE
system.swap.size[,pfree]
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
The system is running out of free memory.
Depends on:
— Lack of available memory ( 0
AVERAGE
High swap space usage (less than <$SWAP.PFREE.MIN.WARN>% free)
This trigger is ignored, if there is no swap configured
Depends on:
— High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
— Lack of available memory ( .+
This macro is used in block devices discovery. Can be overridden on the host or linked template level
Disk read average response time (in ms) before the trigger would fire
Disk write average response time (in ms) before the trigger would fire
Template links
There are no template links in this template.
Discovery rules
Name
Description
Type
Key and additional info
Block devices discovery
ZABBIX_ACTIVE
vfs.dev.discovery
Preprocessing:
Filter:
— A: <#DEVTYPE>MATCHES_REGEX disk
Items collected
Group
Name
Description
Type
Key and additional info
Storage
<#DEVNAME>: Disk read rate
r/s. The number (after merges) of read requests completed per second for the device.
DEPENDENT
vfs.dev.read.rate[<#DEVNAME>]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk write rate
w/s. The number (after merges) of write requests completed per second for the device.
DEPENDENT
vfs.dev.write.rate[<#DEVNAME>]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk read request avg waiting time (r_await)
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.
<#DEVNAME>: Disk write request avg waiting time (w_await)
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.
Rate of total read time counter. Used in r_await calculation
DEPENDENT
vfs.dev.read.time.rate[<#DEVNAME>]
Preprocessing:
Zabbix_raw_items
<#DEVNAME>: Disk write time (rate)
Rate of total write time counter. Used in w_await calculation
DEPENDENT
vfs.dev.write.time.rate[<#DEVNAME>]
Preprocessing:
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
<#DEVNAME>: Disk read/write request responses are too high (read > <$VFS.DEV.READ.AWAIT.WARN:"<#DEVNAME>«> ms for 15m or write > <$VFS.DEV.WRITE.AWAIT.WARN:"<#DEVNAME>«> ms for 15m)
This trigger might indicate disk <#DEVNAME>saturation.
Manual close: YES
Feedback
Please report any issues with the template at https://support.zabbix.com
Linux network interfaces by Zabbix agent active
Overview
For Zabbix version: 5.0 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Filter out loopbacks, nulls, docker veth links and docker0 bridge by default
Interface <#IFNAME>: High error rate (> <$IF.ERRORS.WARN:"<#IFNAME>«> for 5m)
Recovers when below 80% of <$IF.ERRORS.WARN:"<#IFNAME>«> threshold
«,errors].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«> or «,errors].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«>
«,errors].max(5m)>
WARNING
Manual close: YES
Depends on:
— Interface <#IFNAME>: Link down
This trigger expression works as follows:
1. Can be triggered if operations status is down.
2. <$IFCONTROL:"<#IFNAME>«>=1 — user can redefine Context macro to value — 0. That marks this interface as not important. No new trigger will be fired if this interface is down.
3. =1) — trigger fires only if operational status was up(1) sometime before. (So, do not fire ‘ethernal off’ interfaces.)
WARNING: if closed manually — won’t fire again on next poll, because of .diff.
<$IFCONTROL:"<#IFNAME>«>=1 and (/operstate»].last()>=2 and /operstate»].diff()>=1)
/operstate»].last()><>2 or <$IFCONTROL:"<#IFNAME>«>=0
AVERAGE
Manual close: YES
Interface <#IFNAME>: Ethernet has changed to lower speed than it was before
This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close.
/type»].change()> 0 and (/type»].last()>=6 or /type»].last()>=1) and (/operstate»].last()><>2)
(/type»].change()>>0 and /type»].prev()>>0) or (/operstate»].last()>=2)
INFO
Manual close: YES
Depends on:
— Interface <#IFNAME>: Link down
Feedback
Please report any issues with the template at https://support.zabbix.com
Known Issues
Description: High interface utilization trigger is removed since currently it is not possible to retrieve interface speed to determine the max bandwidth.
Linux generic by Zabbix agent active
Overview
For Zabbix version: 5.0 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Template links
There are no template links in this template.
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
General
System boot time
ZABBIX_ACTIVE
system.boottime
Preprocessing:
System local time of the host.
ZABBIX_ACTIVE
system.localtime
General
System name
System host name.
ZABBIX_ACTIVE
system.hostname
Preprocessing:
The information as normally returned by ‘uname -a’.
ZABBIX_ACTIVE
system.uname
Preprocessing:
General
Number of logged in users
Number of users who are currently logged in.
ZABBIX_ACTIVE
system.users.num
General
Maximum number of open file descriptors
It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf.
ZABBIX_ACTIVE
kernel.maxfiles
Preprocessing:
General
Maximum number of processes
It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf.
ZABBIX_ACTIVE
kernel.maxproc
Preprocessing:
ZABBIX_ACTIVE
proc.num
General
Number of running processes
ZABBIX_ACTIVE
proc.num[,,run]
Inventory
Operating system
ZABBIX_ACTIVE
system.sw.os
Preprocessing:
Inventory
Operating system architecture
Operating system architecture of the host.
ZABBIX_ACTIVE
system.sw.arch
Preprocessing:
ZABBIX_ACTIVE
system.sw.packages
Preprocessing:
Security
Checksum of /etc/passwd
ZABBIX_ACTIVE
vfs.file.cksum[/etc/passwd]
Preprocessing:
System uptime in ‘N days, hh:mm:ss’ format.
ZABBIX_ACTIVE
system.uptime
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
System time is out of sync (diff with Zabbix server > <$SYSTEM.FUZZYTIME.MAX>s)
The host system time is different from the Zabbix server time.
Manual close: YES
System name has changed (new name: )
System name has changed. Ack to close.
Manual close: YES
Configured max number of open filedescriptors is too low (
INFO
Configured max number of processes is too low (
INFO
Depends on:
— Getting closer to process limit (over 80% used)
Getting closer to process limit (over 80% used)
/*100>80
WARNING
Operating system description has changed
Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.
Manual close: YES
Depends on:
— System name has changed (new name: )
Manual close: YES
Depends on:
— Operating system description has changed
— System name has changed (new name: )
has been restarted (uptime
WARNING
Manual close: YES
Feedback
Please report any issues with the template at https://support.zabbix.com
Linux by Zabbix agent active
Overview
For Zabbix version: 5.0 and higher New official Linux template. Requires agent of Zabbix 3.0.14, 3.4.5 and 4.0.0 or newer.
Setup
Install Zabbix agent on Linux OS according to Zabbix documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Template links
Name
Linux CPU by Zabbix agent active
Linux block devices by Zabbix agent active
Linux filesystems by Zabbix agent active
Linux generic by Zabbix agent active
Linux memory by Zabbix agent active
Linux network interfaces by Zabbix agent active
Zabbix agent
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide a feedback, discuss the template or ask for help with it at ZABBIX forums.
Known Issues
Description: Network discovery. Zabbix agent as of 4.2 doesn’t support items such as net.if.status, net.if.speed.
Also available for: 5.0
Linux memory SNMP
Overview
For Zabbix version: 5.4 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Template links
There are no template links in this template.
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Memory
Memory utilization
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.
Memory used by kernel buffers (Buffers in /proc/meminfo)
SNMP
vm.memory.buffers[memBuffer.0]
Preprocessing:
Memory used by the page cache and slabs (Cached and Slab in /proc/meminfo)
SNMP
vm.memory.cached[memCached.0]
Preprocessing:
Total memory in Bytes
SNMP
vm.memory.total[memTotalReal.0]
Preprocessing:
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.
This macro is used in filesystems discovery. Can be overridden on the host or linked template level
Template links
There are no template links in this template.
Discovery rules
Name
Description
Type
Key and additional info
Mounted filesystem discovery
HOST-RESOURCES-MIB::hrStorage discovery with storage filter
SNMP
vfs.fs.discovery[snmp]
Filter:
Items collected
Group
Name
Description
Type
Key and additional info
Storage
<#FSNAME>: Used space
The amount of the storage represented by this entry that is allocated, in units of hrStorageAllocationUnits.
SNMP
vfs.fs.used[hrStorageUsed.<#SNMPINDEX>]
Preprocessing:
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.
If having problems collecting this item make sure access to UCD-SNMP-MIB is allowed.
SNMP
vfs.fs.inode.pfree[dskPercentNode.<#SNMPINDEX>]
Preprocessing:
— JAVASCRIPT: return (100-value);
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
<#FSNAME>: Disk space is critically low (used > <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>%)
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 5G.
— The disk will be full in less than 24 hours.
Manual close: YES
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 10G.
— The disk will be full in less than 24 hours.
Manual close: YES
Depends on:
<#FSNAME>: Running out of free inodes (free ].min(5m)>
AVERAGE
<#FSNAME>: Running out of free inodes (free ].min(5m)>
WARNING
Depends on:
— <#FSNAME>: Running out of free inodes (free snmpconf :
Change <$SNMP_COMMUNITY>on the host level in Zabbix.
Zabbix configuration
No specific Zabbix configuration is required.
Template links
Name
EtherLike-MIB SNMP
Generic SNMP
Interfaces SNMP
Linux CPU SNMP
Linux block devices SNMP
Linux filesystems SNMP
Linux memory SNMP
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide a feedback, discuss the template or ask for help with it at ZABBIX forums.
References
Also available for: 5.4
Linux memory SNMP
Overview
For Zabbix version: 5.0 and higher
Setup
Refer to the vendor documentation.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Template links
There are no template links in this template.
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Memory
Memory utilization
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.
Memory used by kernel buffers (Buffers in /proc/meminfo)
SNMP
vm.memory.buffers[memBuffer.0]
Preprocessing:
Memory used by the page cache and slabs (Cached and Slab in /proc/meminfo)
SNMP
vm.memory.cached[memCached.0]
Preprocessing:
Total memory in Bytes
SNMP
vm.memory.total[memTotalReal.0]
Preprocessing:
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.
This macro is used in filesystems discovery. Can be overridden on the host or linked template level
Template links
There are no template links in this template.
Discovery rules
Name
Description
Type
Key and additional info
Mounted filesystem discovery
HOST-RESOURCES-MIB::hrStorage discovery with storage filter
SNMP
vfs.fs.discovery[snmp]
Filter:
Items collected
Group
Name
Description
Type
Key and additional info
Storage
<#FSNAME>: Used space
The amount of the storage represented by this entry that is allocated, in units of hrStorageAllocationUnits.
SNMP
vfs.fs.used[hrStorageUsed.<#SNMPINDEX>]
Preprocessing:
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.
If having problems collecting this item make sure access to UCD-SNMP-MIB is allowed.
SNMP
vfs.fs.inode.pfree[dskPercentNode.<#SNMPINDEX>]
Preprocessing:
— JAVASCRIPT: return (100-value);
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
<#FSNAME>: Disk space is critically low (used > <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>%)
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 5G.
— The disk will be full in less than 24 hours.
Manual close: YES
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 10G.
— The disk will be full in less than 24 hours.
Manual close: YES
Depends on:
<#FSNAME>: Running out of free inodes (free ].min(5m)>
AVERAGE
<#FSNAME>: Running out of free inodes (free ].min(5m)>
WARNING
Depends on:
— <#FSNAME>: Running out of free inodes (free snmpconf :
Change <$SNMP_COMMUNITY>on the host level in Zabbix.
Zabbix configuration
No specific Zabbix configuration is required.
Template links
Name
EtherLike-MIB SNMP
Generic SNMP
Interfaces SNMP
Linux CPU SNMP
Linux block devices SNMP
Linux filesystems SNMP
Linux memory SNMP
Discovery rules
Items collected
Group
Name
Description
Type
Key and additional info
Triggers
Name
Description
Expression
Severity
Dependencies and additional info
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide a feedback, discuss the template or ask for help with it at ZABBIX forums.
References
Also available for: 5.0
Linux by Prom
Overview
For Zabbix version: 5.4 and higher This template collects Linux metrics from node_exporter 0.18 and above. Support for older node_exporter versions is provided as ‘best effort’.
This template was tested on:
node_exporter, version 0.17.0
node_exporter, version 0.18.1
Setup
Please refer to the node_exporter docs. Use node_exporter v0.18.0 or above.
Zabbix configuration
No specific Zabbix configuration is required.
Macros used
Load per CPU considered sustainable. Tune if needed.
Filter out loopbacks, nulls, docker veth links and docker0 bridge by default
Available memory, in Linux, available = free + buffers + cache. On other platforms calculation may vary. See also: https://www.zabbix.com/documentation/5.4/manual/appendix/items/vm.memory.size_params
— JAVASCRIPT: Text is too long. Please see the template.
r/s. The number (after merges) of read requests completed per second for the device.
DEPENDENT
vfs.dev.read.rate[node_exporter,»<#DEVNAME>«]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk write rate
w/s. The number (after merges) of write requests completed per second for the device.
DEPENDENT
vfs.dev.write.rate[node_exporter,»<#DEVNAME>«]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk read request avg waiting time (r_await)
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.
<#DEVNAME>: Disk write request avg waiting time (w_await)
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.
Load average is too high (per CPU load over <$LOAD_AVG_PER_CPU.MAX.WARN>for 5m)
Per CPU load average is too high. Your system may be slow to respond.
/> <$LOAD_AVG_PER_CPU.MAX.WARN>and >0 and >0
AVERAGE
High CPU utilization (over <$CPU.UTIL.CRIT>% for 5m)
CPU utilization is too high. The system might be slow to respond.
Depends on:
— Load average is too high (per CPU load over <$LOAD_AVG_PER_CPU.MAX.WARN>for 5m)
System time is out of sync (diff with Zabbix server > <$SYSTEM.FUZZYTIME.MAX>s)
The host system time is different from the Zabbix server time.
Manual close: YES
System name has changed (new name: )
System name has changed. Ack to close.
Manual close: YES
Configured max number of open filedescriptors is too low (
INFO
Depends on:
— Running out of file descriptors (less than /*100>80
WARNING
Operating system description has changed
Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.
Manual close: YES
Depends on:
— System name has changed (new name: )
High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
The system is running out of free memory.
Depends on:
— Lack of available memory ( 0
AVERAGE
High swap space usage (less than <$SWAP.PFREE.MIN.WARN>% free)
This trigger is ignored, if there is no swap configured
Depends on:
— High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
— Lack of available memory ( <$IF.UTIL.MAX:"<#IFNAME>«>% )
The network interface utilization is close to its estimated maximum bandwidth.
(«].avg(15m)>>(<$IF.UTIL.MAX:"<#IFNAME>«>/100)*«].last()> or «].avg(15m)>>(<$IF.UTIL.MAX:"<#IFNAME>«>/100)*«].last()>) and «].last()>>0
«].avg(15m)>
WARNING
Manual close: YES
Depends on:
Interface <#IFNAME>(<#IFALIAS>): High error rate (> <$IF.ERRORS.WARN:"<#IFNAME>«> for 5m)
Recovers when below 80% of <$IF.ERRORS.WARN:"<#IFNAME>«> threshold
«].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«> or «].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«>
«].max(5m)>
WARNING
Manual close: YES
Depends on:
Interface <#IFNAME>(<#IFALIAS>): Ethernet has changed to lower speed than it was before
This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close.
«].change()> 0 and («].last()>=6 or «].last()>=7 or «].last()>=11 or «].last()>=62 or «].last()>=69 or «].last()>=117 ) and («].last()><>2)
(«].change()>>0 and «].prev()>>0) or («].last()>=2)
INFO
Manual close: YES
Depends on:
Interface <#IFNAME>(<#IFALIAS>): Ethernet has changed to lower speed than it was before
This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close.
«].change()> 0 and («].last()>=6 or «].last()>=1) and («].last()><>2)
(«].change()>>0 and «].prev()>>0) or («].last()>=2)
INFO
Manual close: YES
Depends on:
This trigger expression works as follows:
1. Can be triggered if operations status is down.
2. <$IFCONTROL:"<#IFNAME>«>=1 — user can redefine Context macro to value — 0. That marks this interface as not important. No new trigger will be fired if this interface is down.
3. =1) — trigger fires only if operational status was up(1) sometime before. (So, do not fire ‘ethernal off’ interfaces.)
WARNING: if closed manually — won’t fire again on next poll, because of .diff.
<$IFCONTROL:"<#IFNAME>«>=1 and («].last()>=2 and «].diff()>=1)
«].last()><>2 or <$IFCONTROL:"<#IFNAME>«>=0
AVERAGE
Manual close: YES
has been restarted (uptime
WARNING
Manual close: YES
<#FSNAME>: Disk space is critically low (used > <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>%)
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 5G.
— The disk will be full in less than 24 hours.
Manual close: YES
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 10G.
— The disk will be full in less than 24 hours.
Manual close: YES
Depends on:
<#FSNAME>: Running out of free inodes (free «].min(5m)>
AVERAGE
<#FSNAME>: Running out of free inodes (free «].min(5m)>
WARNING
Depends on:
— <#FSNAME>: Running out of free inodes (free <$VFS.DEV.READ.AWAIT.WARN:"<#DEVNAME>«> ms for 15m or write > <$VFS.DEV.WRITE.AWAIT.WARN:"<#DEVNAME>«> ms for 15m)
This trigger might indicate disk <#DEVNAME>saturation.
Manual close: YES
node_exporter is not available (or no data for 30m)
Failed to fetch system metrics from node_exporter in time.
Manual close: YES
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide a feedback, discuss the template or ask for help with it at ZABBIX forums.
Known Issues
Description: node_exporter v0.16.0 renamed many metrics. CPU utilization for ‘guest’ and ‘guest_nice’ metrics are not supported in this template with node_exporter 90
Load per CPU considered sustainable. Tune if needed.
Filter out loopbacks, nulls, docker veth links and docker0 bridge by default
Available memory, in Linux, available = free + buffers + cache. On other platforms calculation may vary. See also: https://www.zabbix.com/documentation/5.0/manual/appendix/items/vm.memory.size_params
— JAVASCRIPT: Text is too long. Please see the template.
r/s. The number (after merges) of read requests completed per second for the device.
DEPENDENT
vfs.dev.read.rate[node_exporter,»<#DEVNAME>«]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk write rate
w/s. The number (after merges) of write requests completed per second for the device.
DEPENDENT
vfs.dev.write.rate[node_exporter,»<#DEVNAME>«]
Preprocessing:
— CHANGE_PER_SECOND
Storage
<#DEVNAME>: Disk read request avg waiting time (r_await)
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.
<#DEVNAME>: Disk write request avg waiting time (w_await)
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.
Load average is too high (per CPU load over <$LOAD_AVG_PER_CPU.MAX.WARN>for 5m)
Per CPU load average is too high. Your system may be slow to respond.
/> <$LOAD_AVG_PER_CPU.MAX.WARN>and >0 and >0
AVERAGE
High CPU utilization (over <$CPU.UTIL.CRIT>% for 5m)
CPU utilization is too high. The system might be slow to respond.
Depends on:
— Load average is too high (per CPU load over <$LOAD_AVG_PER_CPU.MAX.WARN>for 5m)
System time is out of sync (diff with Zabbix server > <$SYSTEM.FUZZYTIME.MAX>s)
The host system time is different from the Zabbix server time.
Manual close: YES
System name has changed (new name: )
System name has changed. Ack to close.
Manual close: YES
Configured max number of open filedescriptors is too low (
INFO
Depends on:
— Running out of file descriptors (less than /*100>80
WARNING
Operating system description has changed
Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.
Manual close: YES
Depends on:
— System name has changed (new name: )
High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
The system is running out of free memory.
Depends on:
— Lack of available memory ( 0
AVERAGE
High swap space usage (less than <$SWAP.PFREE.MIN.WARN>% free)
This trigger is ignored, if there is no swap configured
Depends on:
— High memory utilization (><$MEMORY.UTIL.MAX>% for 5m)
— Lack of available memory ( <$IF.UTIL.MAX:"<#IFNAME>«>% )
The network interface utilization is close to its estimated maximum bandwidth.
(«].avg(15m)>>(<$IF.UTIL.MAX:"<#IFNAME>«>/100)*«].last()> or «].avg(15m)>>(<$IF.UTIL.MAX:"<#IFNAME>«>/100)*«].last()>) and «].last()>>0
«].avg(15m)>
WARNING
Manual close: YES
Depends on:
Interface <#IFNAME>(<#IFALIAS>): High error rate (> <$IF.ERRORS.WARN:"<#IFNAME>«> for 5m)
Recovers when below 80% of <$IF.ERRORS.WARN:"<#IFNAME>«> threshold
«].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«> or «].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«>
«].max(5m)>
WARNING
Manual close: YES
Depends on:
Interface <#IFNAME>(<#IFALIAS>): Ethernet has changed to lower speed than it was before
This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close.
«].change()> 0 and («].last()>=6 or «].last()>=7 or «].last()>=11 or «].last()>=62 or «].last()>=69 or «].last()>=117 ) and («].last()><>2)
(«].change()>>0 and «].prev()>>0) or («].last()>=2)
INFO
Manual close: YES
Depends on:
Interface <#IFNAME>(<#IFALIAS>): Ethernet has changed to lower speed than it was before
This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close.
«].change()> 0 and («].last()>=6 or «].last()>=1) and («].last()><>2)
(«].change()>>0 and «].prev()>>0) or («].last()>=2)
INFO
Manual close: YES
Depends on:
This trigger expression works as follows:
1. Can be triggered if operations status is down.
2. <$IFCONTROL:"<#IFNAME>«>=1 — user can redefine Context macro to value — 0. That marks this interface as not important. No new trigger will be fired if this interface is down.
3. =1) — trigger fires only if operational status was up(1) sometime before. (So, do not fire ‘ethernal off’ interfaces.)
WARNING: if closed manually — won’t fire again on next poll, because of .diff.
<$IFCONTROL:"<#IFNAME>«>=1 and («].last()>=2 and «].diff()>=1)
«].last()><>2 or <$IFCONTROL:"<#IFNAME>«>=0
AVERAGE
Manual close: YES
has been restarted (uptime
WARNING
Manual close: YES
<#FSNAME>: Disk space is critically low (used > <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>%)
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 5G.
— The disk will be full in less than 24 hours.
Manual close: YES
Two conditions should match: First, space utilization should be above <$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«>.
Second condition should be one of the following:
— The disk free space is less than 10G.
— The disk will be full in less than 24 hours.
Manual close: YES
Depends on:
<#FSNAME>: Running out of free inodes (free «].min(5m)>
AVERAGE
<#FSNAME>: Running out of free inodes (free «].min(5m)>
WARNING
Depends on:
— <#FSNAME>: Running out of free inodes (free <$VFS.DEV.READ.AWAIT.WARN:"<#DEVNAME>«> ms for 15m or write > <$VFS.DEV.WRITE.AWAIT.WARN:"<#DEVNAME>«> ms for 15m)
This trigger might indicate disk <#DEVNAME>saturation.
Manual close: YES
node_exporter is not available (or no data for 30m)
Failed to fetch system metrics from node_exporter in time.
Manual close: YES
Feedback
Please report any issues with the template at https://support.zabbix.com
You can also provide a feedback, discuss the template or ask for help with it at ZABBIX forums.
