recovery expression (optional) - defines additional conditions of the problem resolution.problem expression - defines the conditions of the problem.While the syntax is exactly the same, from the functional point of view there are two types of trigger expressions: Will trigger if the number of received bytes during the last five minutes was always over 100 kilobytes. Max(/Linux by Zabbix agent/vm.memory.Min(/Zabbix server/net.if.in,5m) > 100K The architecture of the operating system.įor passive only agents, host availability is used with It could be increased by using sysctl utility or modifying the file /etc/nf. Linux: Maximum number of open file descriptors The number of users who are currently logged in. The information as normally returned by uname -a. The system uptime expressed in the following format: "N days, hh:mm:ss". The free space of the swap volume/file expressed in %. The free space of the swap volume/file expressed in bytes. The total space of the swap volume/file expressed in bytes. See also Appendixes in Zabbix Documentation about parameters of the vm.memory.size item. on other platforms calculation may vary. in Linux - available = free + buffers + cache The available memory as percentage of the total. The percentage of used memory is calculated as 100-pavailable. Later to be extracted by preprocessing in dependent items. The vfs.fs.get key acquires raw information set about the file systems. The time spent on running a niced guest (a virtual CPU for guest operating systems under the control of the Linux kernel). Guest time - the time spent on running a virtual CPU for a guest operating system. The amount of time the CPU has been servicing software interrupts. The amount of time the CPU has been servicing hardware interrupts. The amount of "stolen" CPU from this virtual machine by the hypervisor for other tasks, such as running another virtual machine. The amount of time the CPU has been waiting for I/O to complete. The time the CPU has spent running users' processes that have been niced. The time the CPU has spent running users' processes that are not niced. The time the CPU has spent running the kernel and its processes. The time the CPU has spent doing nothing. JavaScript: //Calculate utilizationreturn (100 - value) Monitoring the availability status of the agent. It could be used in combination with nodata() for availability check. The agent always returns 1 for this item. This macro is used as a threshold in the interface utilization trigger. It filters out loopbacks, nulls, docker veth links and docker0 bridge by default. It can be overridden on host level or its linked template level. This macro is used for a discovery of block devices. The average response time (in ms) of disk write before the trigger would fire. The average response time (in ms) of disk read before the trigger would fire. This macro is used as a threshold in the memory available trigger. This macro is used as a threshold in the memory utilization trigger. The warning threshold of the filesystem utilization. The critical threshold of the filesystem utilization. The warning threshold of the filesystem metadata utilization. The critical threshold of the filesystem metadata utilization. The warning threshold for utilization of the filesystem. The critical threshold for utilization of the filesystem. This macro is used for discovery of the filesystems. The CPU load per core is considered sustainable. Works only for agents reachable from Zabbix server/proxy (passive mode). Timeout after which agent is considered unavailable. Install Zabbix agent on Linux OS following Zabbix documentation. Zabbix should be configured according to the instructions in the Templates out of the box section.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |