Memory usage linux zabbix

Подобным образом добавляем остальные тригеры (для использования процессора и количества процессов):

5. Конфигурация хоста

Теперь мы можем добавить наш шаблон к хосту. Идем в Configuration -> Hosts -> ваш сервер -> Templates. И добавляем только что созданный шаблон к серверу. Далее мы должны переопределись макросы.

Для примера на нашем сервере необходимо мониторить процесс node (node.js). Давайте посмотрим один из моих графиков данного процесса:

Вы видите, что у меня он потребляет порядка 4Gb RAM. Это нормальное состояние для моего сервиса. Так же вы видите колебание в районе красной линии. Без гистерезиса Zabbix нас просто заспамил бы сообщениями об изменении статуса в районе этой линии. В моем примере нормальное значение потребления памяти для указания в гистерезисе это 4G, а максимальное – больше чем 4.20G, пусть будет 4,5G. Добавим эти значения, а так же имя нашего процесса как макросы для данного хоста:

Итак, мой триггер перейдет в состоянии PROBLEM только когда значение потребляемой памяти будет больше чем 4,5Gb 3 раза подряд. А вернется он в нормальное состояние только тогда, когда потребление снизится ниже 4Г 3 раза подряд.

Готово! Позравляю! Теперь можно проверить последние данные в разделе Monitoring -> Latest data.

Источник

Memory usage linux zabbix

Toolkit to enable effective monitoring with Zabbix use of memory by individual users.

There is the ansible role, which configures Zabbix agent for monitoring memory. As well as a script that creates a Zabbix graph using a low level discovered items.

To use this software do you need Zabbix server and least one Zabbix agent running. You must have administrative privileges to make changes in the configuration of these tools.

To run the project, use the Ansible role to install script /ansible_role/templates/zabbix_memory.py and provide linux_memory.rss[*] and linux_memory.discovery_user user parameter in Zabbix Agent.

You can use for that following playbook:

Next to import /zbx_export_templates.xml in Zabbix server and use fresh Template memory usage template in some server.

• ID of prototype item rule by Configuration-> Hosts -> some.host.example.com -> Discovery rules -> Discovery system users and lookup URL,
• ID of host by Configuration -> Host -> some.host.example.com and lookup URL.

After collection some data use zabbix-discovered-chart.py to add chart by execution eg. python zabbix-discovered-chart.py **URL** **LOGIN** **PASS** **ITEMID** **HOSTID** .

After all new diagram of name «Memory usage graph» should occurs in Zabbix server. See zabbix-discovered-chart.py —help for details.

Add additional notes about how to deploy this on a live system

This project is licensed under the MIT License — see the LICENSE.md file for details

About

Toolkit to enable effective monitoring with Zabbix use of memory by individual users.

Источник

Zabbix: Difference between «memory usage» and «memory utilization»

I recently started using Zabbix for monitoring, and there is a question I can’t figure out on my own. 🙂 Is «memory usage» kind of inverse function of the «memory utilization»? I have high percentage of the «utilization» and low count on the «usage».

Thanks in advance.

1 Answer 1

Memory usage or utilization etc. are probably item names. You should look into the Template your are using and locate the corresponding key to understand the value.

For instance, in my Zabbix Server 4.4 the Template Module Linux memory by Zabbix agent template has a Memory utilization item with this key: vm.memory.size[pavailable]

pavailable — ‘available’ memory as percentage of ‘total’ (calculated as available/total*100)

Depending on the parameter key, you can extract various memory informations:

Parameters The following parameters are available for this item:

active — memory currently in use or very recently used, and so it is in RAM

anon — memory not associated with a file (cannot be re-read from it)

available — available memory, calculated differently depending on the platform (see the table below)

buffers — cache for things like file system metadata

cached — cache for various things

See which one are you using and maybe try to implement additional items with these parameters to have a first hand experience.

Источник

Memory usage linux zabbix

Linux CPU by Zabbix agent

For Zabbix version: 5.4 and higher

Refer to the vendor documentation.

No specific Zabbix configuration is required.

Load per CPU considered sustainable. Tune if needed.

There are no template links in this template.

CPU utilization in %

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

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

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

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

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

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

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

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

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

Group	Name	Description	Type	Key and additional info
CPU	Number of CPUs	ZABBIX_PASSIVE	system.cpu.num Preprocessing:	ZABBIX_PASSIVE	system.cpu.load[all,avg1]
CPU	Load average (5m avg)	ZABBIX_PASSIVE	system.cpu.load[all,avg5]
CPU	Load average (15m avg)	ZABBIX_PASSIVE	system.cpu.load[all,avg15]
CPU	CPU utilization	DEPENDENT	system.cpu.util Preprocessing: — JAVASCRIPT: //Calculate utilization return (100 — value) The time the CPU has spent doing nothing.	ZABBIX_PASSIVE	system.cpu.util[,idle]
CPU	CPU system time	ZABBIX_PASSIVE	system.cpu.util[,system]
CPU	CPU user time	ZABBIX_PASSIVE	system.cpu.util[,user]
CPU	CPU nice time	ZABBIX_PASSIVE	system.cpu.util[,nice]
CPU	CPU iowait time	ZABBIX_PASSIVE	system.cpu.util[,iowait]
CPU	CPU steal time	ZABBIX_PASSIVE	system.cpu.util[,steal]
CPU	CPU interrupt time	ZABBIX_PASSIVE	system.cpu.util[,interrupt]
CPU	CPU softirq time	ZABBIX_PASSIVE	system.cpu.util[,softirq]
CPU	CPU guest time	ZABBIX_PASSIVE	system.cpu.util[,guest]
CPU	CPU guest nice time	ZABBIX_PASSIVE	system.cpu.util[,guest_nice]
CPU	Context switches per second	ZABBIX_PASSIVE	system.cpu.switches Preprocessing:	ZABBIX_PASSIVE	system.cpu.intr Preprocessing: Per CPU load average is too high. Your system may be slow to respond. CPU utilization is too high. The system might be slow to respond. Depends on: — Load average is too high (per CPU load over <$LOAD_AVG_PER_CPU.MAX.WARN>for 5m) Please report any issues with the template at https://support.zabbix.com Linux filesystems by Zabbix agent For Zabbix version: 5.4 and higher Refer to the vendor documentation. No specific Zabbix configuration is required. This macro is used in filesystems discovery. Can be overridden on the host or linked template level This macro is used in filesystems discovery. Can be overridden on the host or linked template level This macro is used in filesystems discovery. Can be overridden on the host or linked template level This macro is used in filesystems discovery. Can be overridden on the host or linked template level There are no template links in this template. Name Description Expression Severity Dependencies and additional info Load average is too high (per CPU load over <$LOAD_AVG_PER_CPU.MAX.WARN>for 5m) /> <$LOAD_AVG_PER_CPU.MAX.WARN>and >0 and >0 AVERAGE High CPU utilization (over <$CPU.UTIL.CRIT>% for 5m) Discovery of file systems of different types. Name Description Type Key and additional info Mounted filesystem discovery ZABBIX_PASSIVE vfs.fs.discovery Filter: Used storage in Bytes Total space in Bytes Space utilization in % for Group Name Description Type Key and additional info Filesystems <#FSNAME>: Used space ZABBIX_PASSIVE vfs.fs.size[<#FSNAME>,used] Filesystems <#FSNAME>: Total space ZABBIX_PASSIVE vfs.fs.size[<#FSNAME>,total] Filesystems <#FSNAME>: Space utilization ZABBIX_PASSIVE vfs.fs.size[<#FSNAME>,pused] Filesystems <#FSNAME>: Free inodes in % ZABBIX_PASSIVE vfs.fs.inode[<#FSNAME>,pfree] 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: Depends on: — <#FSNAME>: Running out of free inodes (free Please report any issues with the template at https://support.zabbix.com Linux memory by Zabbix agent For Zabbix version: 5.4 and higher Refer to the vendor documentation. No specific Zabbix configuration is required. This macro is used as a threshold in memory available trigger. This macro is used as a threshold in memory utilization trigger. There are no template links in this template. Name Description Expression Severity Dependencies and additional info <#FSNAME>: Disk space is critically low (used > <$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«>%) ,pused].last()>><$VFS.FS.PUSED.MAX.CRIT:"<#FSNAME>«> and ((,total].last()>-,used].last()>) AVERAGE ,pused].last()>><$VFS.FS.PUSED.MAX.WARN:"<#FSNAME>«> and ((,total].last()>-,used].last()>) WARNING <#FSNAME>: Running out of free inodes (free ,pfree].min(5m)> AVERAGE <#FSNAME>: Running out of free inodes (free ,pfree].min(5m)> WARNING Memory used percentage is calculated as (100-pavailable) Total memory in Bytes Available memory, in Linux, available = free + buffers + cache. On other platforms calculation may vary. See also: https://www.zabbix.com/documentation/6.0/manual/appendix/items/vm.memory.size_params The total space of swap volume/file in bytes. The free space of swap volume/file in bytes. The free space of swap volume/file in percent. Group Name Description Type Key and additional info Memory Memory utilization DEPENDENT vm.memory.utilization Preprocessing: — JAVASCRIPT: return (100-value); ZABBIX_PASSIVE vm.memory.size[pavailable] Memory Total memory ZABBIX_PASSIVE vm.memory.size[total] Memory Available memory ZABBIX_PASSIVE vm.memory.size[available] Memory Total swap space ZABBIX_PASSIVE system.swap.size[,total] Memory Free swap space ZABBIX_PASSIVE system.swap.size[,free] Memory Free swap space in % ZABBIX_PASSIVE system.swap.size[,pfree] The system is running out of free memory. Depends on: — Lack of available memory ( 0 This trigger is ignored, if there is no swap configured Depends on: — High memory utilization (><$MEMORY.UTIL.MAX>% for 5m) — Lack of available memory ( Please report any issues with the template at https://support.zabbix.com Linux block devices by Zabbix agent For Zabbix version: 5.4 and higher Refer to the vendor documentation. No specific Zabbix configuration is required. This macro is used in block devices discovery. Can be overridden on the host or linked template level This macro is used in block devices discovery. Can be overridden on the host or linked template level Disk read average response time (in ms) before the trigger would fire Disk write average response time (in ms) before the trigger would fire There are no template links in this template. Name Description Expression Severity Dependencies and additional info High memory utilization (><$MEMORY.UTIL.MAX>% for 5m) AVERAGE High swap space usage (less than <$SWAP.PFREE.MIN.WARN>% free) Name Description Type Key and additional info Block devices discovery ZABBIX_PASSIVE vfs.dev.discovery Preprocessing: Filter: — A: <#DEVTYPE>MATCHES_REGEX disk r/s. The number (after merges) of read requests completed per second for the device. This formula contains two boolean expressions that evaluates to 1 or 0 in order to set calculated metric to zero and to avoid division by zero exception. This formula contains two boolean expressions that evaluates to 1 or 0 in order to set calculated metric to zero and to avoid division by zero exception. Current average disk queue, the number of requests outstanding on the disk at the time the performance data is collected. Rate of total read time counter. Used in r_await calculation Rate of total write time counter. Used in w_await calculation Group Name Description Type Key and additional info Storage <#DEVNAME>: Disk read rate DEPENDENT vfs.dev.read.rate[<#DEVNAME>] Preprocessing: w/s. The number (after merges) of write requests completed per second for the device. DEPENDENT vfs.dev.write.rate[<#DEVNAME>] Preprocessing: Storage <#DEVNAME>: Disk read request avg waiting time (r_await) CALCULATED vfs.dev.read.await[<#DEVNAME>] Expression: (last(«vfs.dev.read.time.rate[<#DEVNAME>]»)/(last(«vfs.dev.read.rate[<#DEVNAME>]»)+(last(«vfs.dev.read.rate[<#DEVNAME>]»)=0)))*1000*(last(«vfs.dev.read.rate[<#DEVNAME>]») > 0) Storage <#DEVNAME>: Disk write request avg waiting time (w_await) CALCULATED vfs.dev.write.await[<#DEVNAME>] Expression: (last(«vfs.dev.write.time.rate[<#DEVNAME>]»)/(last(«vfs.dev.write.rate[<#DEVNAME>]»)+(last(«vfs.dev.write.rate[<#DEVNAME>]»)=0)))*1000*(last(«vfs.dev.write.rate[<#DEVNAME>]») > 0) Storage <#DEVNAME>: Disk average queue size (avgqu-sz) DEPENDENT vfs.dev.queue_size[<#DEVNAME>] Preprocessing: This item is the percentage of elapsed time that the selected disk drive was busy servicing read or writes requests. DEPENDENT vfs.dev.util[<#DEVNAME>] Preprocessing: Get contents of /sys/block/<#DEVNAME>/stat for disk stats. ZABBIX_PASSIVE vfs.file.contents[/sys/block/<#DEVNAME>/stat] Preprocessing: — JAVASCRIPT: return JSON.stringify(value.trim().split(/ +/)); Zabbix_raw_items <#DEVNAME>: Disk read time (rate) DEPENDENT vfs.dev.read.time.rate[<#DEVNAME>] Preprocessing: Zabbix_raw_items <#DEVNAME>: Disk write time (rate) DEPENDENT vfs.dev.write.time.rate[<#DEVNAME>] Preprocessing: This trigger might indicate disk <#DEVNAME>saturation. Manual close: YES Please report any issues with the template at https://support.zabbix.com Linux network interfaces by Zabbix agent For Zabbix version: 5.4 and higher Refer to the vendor documentation. No specific Zabbix configuration is required. Filter out loopbacks, nulls, docker veth links and docker0 bridge by default 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) `(^Software Loopback Interface There are no template links in this template. Discovery of network interfaces. Indicates the interface RFC2863 operational state as a string. Possible values are:»unknown», «notpresent», «down», «lowerlayerdown», «testing»,»dormant», «up». Indicates the interface protocol type as a decimal value. See include/uapi/linux/if_arp.h for all possible values. Name Description Type Key and additional info Network interface discovery ZABBIX_PASSIVE net.if.discovery Filter: Group Name Description Type Key and additional info Network_interfaces Interface <#IFNAME>: Bits received ZABBIX_PASSIVE net.if.in[«<#IFNAME>«] Preprocessing: Network_interfaces Interface <#IFNAME>: Bits sent ZABBIX_PASSIVE net.if.out[«<#IFNAME>«] Preprocessing: Network_interfaces Interface <#IFNAME>: Outbound packets with errors ZABBIX_PASSIVE net.if.out[«<#IFNAME>«,errors] Preprocessing: Network_interfaces Interface <#IFNAME>: Inbound packets with errors ZABBIX_PASSIVE net.if.in[«<#IFNAME>«,errors] Preprocessing: Network_interfaces Interface <#IFNAME>: Outbound packets discarded ZABBIX_PASSIVE net.if.out[«<#IFNAME>«,dropped] Preprocessing: Network_interfaces Interface <#IFNAME>: Inbound packets discarded ZABBIX_PASSIVE net.if.in[«<#IFNAME>«,dropped] Preprocessing: Network_interfaces Interface <#IFNAME>: Operational status ZABBIX_PASSIVE vfs.file.contents[«/sys/class/net/<#IFNAME>/operstate»] Preprocessing: — JAVASCRIPT: Text is too long. Please see the template. Network_interfaces Interface <#IFNAME>: Interface type ZABBIX_PASSIVE vfs.file.contents[«/sys/class/net/<#IFNAME>/type»] Preprocessing: Recovers when below 80% of <$IF.ERRORS.WARN:"<#IFNAME>«> threshold 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. Manual close: YES This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Ack to close. Manual close: YES Depends on: — Interface <#IFNAME>: Link down Please report any issues with the template at https://support.zabbix.com 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 For Zabbix version: 5.4 and higher Refer to the vendor documentation. No specific Zabbix configuration is required. There are no template links in this template. Name Description Expression Severity Dependencies and additional info Interface <#IFNAME>: High error rate (> <$IF.ERRORS.WARN:"<#IFNAME>«> for 5m) «,errors].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«> or «,errors].min(5m)>><$IF.ERRORS.WARN:"<#IFNAME>«> «,errors].max(5m)> WARNING <$IFCONTROL:"<#IFNAME>«>=1 and (/operstate»].last()>=2 and /operstate»].diff()>=1) /operstate»].last()><>2 or <$IFCONTROL:"<#IFNAME>«>=0 AVERAGE Interface <#IFNAME>: Ethernet has changed to lower speed than it was before /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 System host name. Number of users who are currently logged in. It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf. It could be increased by using sysctrl utility or modifying file /etc/sysctl.conf. Operating system architecture of the host. 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 ZABBIX_PASSIVE system.hostname Preprocessing: The information as normally returned by ‘uname -a’. ZABBIX_PASSIVE system.uname Preprocessing: General Number of logged in users ZABBIX_PASSIVE system.users.num General Maximum number of open file descriptors ZABBIX_PASSIVE kernel.maxfiles Preprocessing: General Maximum number of processes 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 ZABBIX_PASSIVE system.sw.arch Preprocessing: ZABBIX_PASSIVE system.sw.packages Preprocessing: Security Checksum of /etc/passwd ZABBIX_PASSIVE vfs.file.cksum[/etc/passwd,sha256] Preprocessing: System uptime in ‘N days, hh:mm:ss’ format. ZABBIX_PASSIVE system.uptime The host system time is different from the Zabbix server time. Manual close: YES System name has changed. Ack to close. Manual close: YES Depends on: — Getting closer to process limit (over 80% used) Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close. Manual close: YES Depends on: — System name has changed (new name: ) Manual close: YES Depends on: — Operating system description has changed — System name has changed (new name: ) Manual close: YES Please report any issues with the template at https://support.zabbix.com Linux by Zabbix agent 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. Install Zabbix agent on Linux OS according to Zabbix documentation. No specific Zabbix configuration is required. Name Description Expression Severity Dependencies and additional info System time is out of sync (diff with Zabbix server > <$SYSTEM.FUZZYTIME.MAX>s) System name has changed (new name: ) Configured max number of open filedescriptors is too low ( INFO Configured max number of processes is too low ( INFO Getting closer to process limit (over 80% used) /*100>80 WARNING Operating system description has changed has been restarted (uptime WARNING 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 Group Name Description Type Key and additional info Name Description Expression Severity Dependencies and additional info 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. Description: Network discovery. Zabbix agent as of 4.2 doesn’t support items such as net.if.status, net.if.speed. You can’t perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. Источник Читайте также:  Ati mobility radeon hd 4250 драйвер для windows 10 Оцените статью Вам также может понравиться Windows или Linux: Что лучше выбрать? Есть много причин выбирать между Windows и Linux, но Файл владелец изменить linux Команда Chown в Linux Chown Command in Linux (File Установка шлюза по умолчанию linux Настройка сети вручную Содержание Краткое описание Чем разбить диск для linux ИТ База знаний Курс по Asterisk Полезно — Узнать IP — Правообладателям Политика конфиденциальности Контакты