diff --git a/zabbix_templates/6.4/custom-os-linux-hardware.xml b/zabbix_templates/6.4/custom-os-linux-hardware.xml index a8b5077..459c1d0 100644 --- a/zabbix_templates/6.4/custom-os-linux-hardware.xml +++ b/zabbix_templates/6.4/custom-os-linux-hardware.xml @@ -46,7 +46,6 @@ 60d 0 TEXT - POST Application @@ -71,7 +70,6 @@ 2h 1w 0 - POST Application @@ -87,7 +85,6 @@ 2h 1w 0 - POST Application @@ -112,7 +109,6 @@ - POST Application @@ -128,7 +124,6 @@ 2h 1w 0 - POST Application @@ -144,7 +139,6 @@ 2h 1w 0 - POST Application @@ -161,7 +155,6 @@ 1w 90d C - POST Application @@ -176,7 +169,6 @@ hardware.disk.smart.attributes[{#BLOCKDEVICE},UDMA_CRC_Error_Count] 2h 1w - POST Application @@ -192,7 +184,6 @@ 1d 0 CHAR - POST Application @@ -208,7 +199,6 @@ 1d 0 CHAR - POST Application @@ -297,7 +287,6 @@ - POST diff --git a/zabbix_templates/6.4/custom-os-linux.xml b/zabbix_templates/6.4/custom-os-linux.xml index 9abf6fe..ebac944 100644 --- a/zabbix_templates/6.4/custom-os-linux.xml +++ b/zabbix_templates/6.4/custom-os-linux.xml @@ -27,7 +27,6 @@ 10m 60d 0 - POST Application @@ -62,7 +61,6 @@ 0 TEXT The release of the zabbix agent - POST Application @@ -94,7 +92,6 @@ 3m 1w Total number of processes in any state. - POST Application @@ -109,7 +106,6 @@ icmpping[,1,,,] 2m 1w - POST Application @@ -148,7 +144,6 @@ 1d 14d files - POST Application @@ -164,7 +159,6 @@ 5m 1w Total number of possible processes. - POST Application @@ -181,7 +175,6 @@ 0 TEXT Reads the output of dmesg and discovers kernel problems. - POST Application @@ -225,7 +218,6 @@ This trigger does not recover automatically, to get rid of this trigger, you hav 0 DISABLED TEXT - POST Application @@ -260,7 +252,6 @@ This trigger does not recover automatically, to get rid of this trigger, you hav 14d 0 messages - POST Application @@ -277,7 +268,6 @@ This trigger does not recover automatically, to get rid of this trigger, you hav 14d 0 messages - POST Application @@ -310,7 +300,6 @@ This trigger does not recover automatically, to get rid of this trigger, you hav Service state - POST Application @@ -336,7 +325,6 @@ This trigger does not recover automatically, to get rid of this trigger, you hav Service state - POST Application @@ -369,7 +357,6 @@ This trigger does not recover automatically, to get rid of this trigger, you hav - POST Application @@ -394,7 +381,6 @@ This trigger does not recover automatically, to get rid of this trigger, you hav - POST Application @@ -428,7 +414,6 @@ This trigger does not recover automatically, to get rid of this trigger, you hav Number of good ntp peer servers (should be at least 3 severs). A man with one watch knows what time it is. A man with two watches is never sure. - POST Application @@ -447,7 +432,6 @@ A man with one watch knows what time it is. A man with two watches is never sure FLOAT ms Round trip communication delay to the remote peer or server (milliseconds) - POST Application @@ -466,7 +450,6 @@ A man with one watch knows what time it is. A man with two watches is never sure FLOAT ms Mean deviation (jitter) in the time reported for that remote peer or server (RMS of difference of multiple time samples, milliseconds) - POST Application @@ -485,7 +468,6 @@ A man with one watch knows what time it is. A man with two watches is never sure FLOAT ms Mean offset (phase) in the times reported between this local host and the remote peer or server (RMS, milliseconds) - POST Application @@ -517,7 +499,6 @@ A man with one watch knows what time it is. A man with two watches is never sure 2w B last(//vm.memory.size[total]) - last(//vm.memory.size[free]) - last(//vm.memory.size[buffers]) - last(//vm.memory.size[cached]) - POST Application @@ -544,7 +525,6 @@ A man with one watch knows what time it is. A man with two watches is never sure - POST Application @@ -582,7 +562,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 2m 1w Number of processes in running state. - POST Application @@ -597,7 +576,6 @@ If memory usage of userspace processes is too high, this typically leads to bad proc.num[,,zomb] 1w Number of processes in running state. - POST Application @@ -612,7 +590,6 @@ If memory usage of userspace processes is too high, this typically leads to bad proc.num[cron,,,] 10m Ubuntu,Debian, ... - POST Application @@ -627,7 +604,6 @@ If memory usage of userspace processes is too high, this typically leads to bad proc.num[crond,,,] 10m 0 - POST Application @@ -642,7 +618,6 @@ If memory usage of userspace processes is too high, this typically leads to bad proc.num[] 1w Total number of processes in any state. - POST Application @@ -665,7 +640,6 @@ If memory usage of userspace processes is too high, this typically leads to bad - POST Application @@ -680,8 +654,6 @@ If memory usage of userspace processes is too high, this typically leads to bad system.cpu.load[,avg5] 5m FLOAT - localhost - POST Application @@ -696,8 +668,6 @@ If memory usage of userspace processes is too high, this typically leads to bad system.cpu.num 8h 7d - localhost - POST Application @@ -712,7 +682,6 @@ If memory usage of userspace processes is too high, this typically leads to bad system.cpu.switches 5m 7d - localhost cs/sec @@ -722,7 +691,6 @@ If memory usage of userspace processes is too high, this typically leads to bad - POST Application @@ -739,7 +707,6 @@ If memory usage of userspace processes is too high, this typically leads to bad DISABLED FLOAT % - POST Application @@ -755,7 +722,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 7d FLOAT % - POST Application @@ -771,7 +737,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 7d FLOAT % - POST Application @@ -803,7 +768,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 7d FLOAT % - POST Application @@ -819,7 +783,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 7d FLOAT % - POST Application @@ -835,7 +798,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 7d FLOAT % - POST Application @@ -867,7 +829,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 7d FLOAT % - POST Application @@ -883,7 +844,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 7d FLOAT % - POST Application @@ -909,7 +869,6 @@ If memory usage of userspace processes is too high, this typically leads to bad - POST Application @@ -935,7 +894,6 @@ If memory usage of userspace processes is too high, this typically leads to bad - POST Application @@ -952,7 +910,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 90d FLOAT % - POST Application @@ -989,7 +946,6 @@ If memory usage of userspace processes is too high, this typically leads to bad system.uptime 10m s - POST Application @@ -1013,7 +969,6 @@ If memory usage of userspace processes is too high, this typically leads to bad system.users.num 1w Number of users who are currently logged in. - POST Application @@ -1029,7 +984,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 5m 1w 26w - POST Application @@ -1045,7 +999,6 @@ If memory usage of userspace processes is too high, this typically leads to bad 10m 0 Indicates if a restart is required after system updates. - POST Application @@ -1077,7 +1030,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 3d 14d files - POST Application @@ -1093,7 +1045,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 2m 2w B - POST Application @@ -1109,7 +1060,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 2m 2w B - POST Application @@ -1125,7 +1075,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 2m 2w B - POST Application @@ -1141,7 +1090,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 2m 2w B - POST Application @@ -1157,7 +1105,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 10m 2w B - POST Application @@ -1175,7 +1122,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 0 TEXT The release of the zabbix agent extensions - POST Application @@ -1241,7 +1187,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re - POST Application @@ -1264,7 +1209,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re - POST Application @@ -1288,7 +1232,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re - POST Application @@ -1318,7 +1261,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re - POST Application @@ -1341,7 +1283,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re - POST Application @@ -1365,7 +1306,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re - POST Application @@ -1467,7 +1407,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re - POST e681e16363464fbf9a7af5311fbeef11 @@ -1496,7 +1435,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 90d FLOAT iops - POST Application @@ -1513,7 +1451,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 90d FLOAT sps - POST Application @@ -1530,7 +1467,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 90d FLOAT iops - POST Application @@ -1558,7 +1494,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 90d FLOAT sps - POST Application @@ -1632,7 +1567,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re - POST 90986d047269451c860d05b15d41ec42 @@ -1714,7 +1648,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 600s 7d i - POST Application @@ -1731,7 +1664,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 7d FLOAT % - POST Application @@ -1769,7 +1701,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 1h 2d i - POST Application @@ -1785,7 +1716,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 600s 7d i - POST Application @@ -1801,7 +1731,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 600s 7d B - POST Application @@ -1818,7 +1747,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 7d FLOAT % - POST Application @@ -1835,7 +1763,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 7d s timeleft(//vfs.fs.size[{#FSNAME},free],2d,0) - POST Application @@ -1860,7 +1787,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 1h 2d B - POST Application @@ -1876,7 +1802,6 @@ Remove the flagfile if you decide that no reboot is required (/var/run/reboot-re 600s 7d B - POST Application @@ -2029,7 +1954,6 @@ Filesystem greater that 1TB are alarmed if the free space of the partion is lowe - POST diff --git a/zabbix_templates/6.4/custom-os-puppet.xml b/zabbix_templates/6.4/custom-os-puppet.xml index f1e4181..2c6cd10 100644 --- a/zabbix_templates/6.4/custom-os-puppet.xml +++ b/zabbix_templates/6.4/custom-os-puppet.xml @@ -27,7 +27,6 @@ Service state - POST Application @@ -68,7 +67,6 @@ puppet[] - POST Application @@ -96,7 +94,6 @@ puppet[] - POST Application @@ -132,7 +129,6 @@ puppet[] - POST Application @@ -142,7 +138,7 @@ 102b0d53cecc4e409deec043523a5f3a - last(/Custom - OS - Puppet/puppet[environment],#1)<>last(/Custom - OS - Puppet/puppet[environment],#2) + last(/Custom - OS - Puppet/puppet[environment],#1)<>last(/Custom - OS - Puppet/puppet[environment],#2) Puppet environment changed from {ITEM.VALUE1} to {ITEM.VALUE2} WARNING @@ -167,7 +163,6 @@ puppet[] - POST Application @@ -194,7 +189,6 @@ puppet[] - POST Application @@ -221,7 +215,6 @@ puppet[] - POST Application @@ -248,7 +241,6 @@ puppet[] - POST Application @@ -275,7 +267,6 @@ puppet[] - POST Application @@ -302,7 +293,6 @@ puppet[] - POST Application @@ -329,7 +319,6 @@ puppet[] - POST Application @@ -356,7 +345,6 @@ puppet[] - POST Application @@ -383,7 +371,6 @@ puppet[] - POST Application @@ -410,7 +397,6 @@ puppet[] - POST Application @@ -438,7 +424,6 @@ puppet[] - POST Application @@ -475,7 +460,6 @@ puppet[] - POST Application @@ -510,7 +494,6 @@ puppet[] - POST Application @@ -553,7 +536,6 @@ puppet[] - POST Application @@ -570,7 +552,6 @@ 3d 0 TEXT - POST Application diff --git a/zabbix_templates/6.4/custom-service-apache.xml b/zabbix_templates/6.4/custom-service-apache.xml index fbec769..587cb83 100644 --- a/zabbix_templates/6.4/custom-service-apache.xml +++ b/zabbix_templates/6.4/custom-service-apache.xml @@ -34,7 +34,6 @@ - POST Application @@ -53,7 +52,6 @@ DISABLED backends Activated Backends - POST Application @@ -72,7 +70,6 @@ DISABLED backends Disabled Backends, no new sessions - POST Application @@ -91,7 +88,6 @@ DISABLED backends Stopped Backends, no request processing - POST Application @@ -121,7 +117,6 @@ - POST Application @@ -138,7 +133,6 @@ 30d tasks Apache workers which are currently in keepalive state - POST Application @@ -155,7 +149,6 @@ 30d tasks Apache workers which are currently reading a request. - POST Application @@ -173,7 +166,6 @@ 30d bytes Average RSS memory used by apache process - POST Application @@ -191,7 +183,6 @@ 30d bytes Biggest RSS memory used by apache process - POST Application @@ -209,7 +200,6 @@ 30d bytes Smallest RSS memory used by apache process - POST Application @@ -227,7 +217,6 @@ 30d bytes Total RSS memory used by apache - POST Application @@ -245,7 +234,6 @@ 0 tasks Total amout of possible apache workers. - POST Application @@ -262,7 +250,6 @@ 30d tasks Apache workers which are currently a request result writing to a client. - POST Application @@ -290,7 +277,6 @@ Service state - POST Application @@ -317,7 +303,6 @@ 30d FLOAT sec - POST Application diff --git a/zabbix_templates/6.4/custom-service-nginx.xml b/zabbix_templates/6.4/custom-service-nginx.xml index ba6946d..1cd7120 100644 --- a/zabbix_templates/6.4/custom-service-nginx.xml +++ b/zabbix_templates/6.4/custom-service-nginx.xml @@ -29,7 +29,6 @@ Service state - POST Application @@ -61,7 +60,6 @@ - POST Application @@ -84,7 +82,6 @@ - POST Application @@ -101,7 +98,6 @@ 30d tasks Apache workers which are currently in keepalive state - POST Application @@ -118,7 +114,6 @@ 30d tasks NGINX workers which are currently reading a request. - POST Application @@ -141,7 +136,6 @@ - POST Application @@ -158,7 +152,6 @@ 30d tasks NGINX workers which are currently a request result writing to a client. - POST Application @@ -175,7 +168,6 @@ 30d FLOAT sec - POST Application diff --git a/zabbix_templates/6.4/custom-service-springboot.xml b/zabbix_templates/6.4/custom-service-springboot.xml index e329e4d..7262944 100644 --- a/zabbix_templates/6.4/custom-service-springboot.xml +++ b/zabbix_templates/6.4/custom-service-springboot.xml @@ -35,7 +35,6 @@ 2h 0 TEXT - POST Application @@ -53,7 +52,6 @@ FLOAT s last(//springboot.uri[{#URI},time])/last(//springboot.uri[{#URI},requests]) - POST Application @@ -87,7 +85,6 @@ springboot.get[{$SPRINGBOOT_BASE_URI}/metrics/http.server.requests,tag=uri:{#URI}] - POST Application @@ -122,7 +119,6 @@ springboot.get[{$SPRINGBOOT_BASE_URI}/metrics/http.server.requests,tag=uri:{#URI}] - POST Application @@ -157,7 +153,6 @@ springboot.get[{$SPRINGBOOT_BASE_URI}/metrics/http.server.requests,tag=uri:{#URI}] - POST Application @@ -194,7 +189,6 @@ - POST diff --git a/zabbix_templates/6.4/custom-service-varnish.xml b/zabbix_templates/6.4/custom-service-varnish.xml index 7c79d7b..5ebfc96 100644 --- a/zabbix_templates/6.4/custom-service-varnish.xml +++ b/zabbix_templates/6.4/custom-service-varnish.xml @@ -36,7 +36,6 @@ - POST Application @@ -60,7 +59,6 @@ - POST Application @@ -88,7 +86,6 @@ - POST Application @@ -116,7 +113,6 @@ - POST Application @@ -144,7 +140,6 @@ - POST Application @@ -172,7 +167,6 @@ - POST Application @@ -200,7 +194,6 @@ - POST Application @@ -228,7 +221,6 @@ - POST Application @@ -256,7 +248,6 @@ - POST Application @@ -284,7 +275,6 @@ - POST Application @@ -312,7 +302,6 @@ - POST Application @@ -340,7 +329,6 @@ - POST Application @@ -368,7 +356,6 @@ - POST Application @@ -397,7 +384,6 @@ - POST Application @@ -425,7 +411,6 @@ - POST Application @@ -453,7 +438,6 @@ - POST Application @@ -481,7 +465,6 @@ - POST Application @@ -509,7 +492,6 @@ - POST Application @@ -537,7 +519,6 @@ - POST Application @@ -565,7 +546,6 @@ - POST Application @@ -593,7 +573,6 @@ - POST Application @@ -621,7 +600,6 @@ - POST Application @@ -649,7 +627,6 @@ - POST Application @@ -677,7 +654,6 @@ - POST Application @@ -705,7 +681,6 @@ - POST Application @@ -733,7 +708,6 @@ - POST Application @@ -761,7 +735,6 @@ - POST Application @@ -789,7 +762,6 @@ - POST Application @@ -806,7 +778,6 @@ N expired objects varnish.stat[n_expired] 60 - localhost CHANGE_PER_SECOND @@ -815,14 +786,12 @@ - POST 6b33d0cd1ce242298d6de19fea75d328 N LRU moved objects varnish.stat[n_lru_moved] 60 - localhost CHANGE_PER_SECOND @@ -831,14 +800,12 @@ - POST 5ddef535ffef4b4690505f7c220efa1d N LRU nuked objects varnish.stat[n_lru_nuked] 60 - localhost CHANGE_PER_SECOND @@ -847,28 +814,24 @@ - POST 468eedb8338c4150888119b7c735dbd7 N struct objectcore varnish.stat[n_objectcore] 60 - POST 84baae82571849a09f949dc02c0f8de3 N struct objecthead varnish.stat[n_objecthead] 60 - POST 79e02e3508284073938a13cb7b0f372b N struct object varnish.stat[n_object] 60 - POST ff94bc53aac04f829677c2371ba5032a @@ -886,7 +849,6 @@ - POST Application @@ -914,7 +876,6 @@ - POST Application @@ -942,7 +903,6 @@ - POST Application @@ -959,7 +919,6 @@ N unresurrected objects varnish.stat[n_vampireobject] 60 - POST dadc546246064b15bb8a3a269325ba3b @@ -968,7 +927,6 @@ 90 14d 90d - POST Application @@ -987,7 +945,6 @@ 90 14d 90d - POST Application @@ -1006,7 +963,6 @@ 90 14d 90d - POST Application @@ -1025,7 +981,6 @@ 90 14d 90d - POST Application @@ -1044,7 +999,6 @@ 90 14d 90d - POST Application @@ -1063,7 +1017,6 @@ 90 14d 90d - POST Application @@ -1082,7 +1035,6 @@ 90 14d 90d - POST Application @@ -1110,7 +1062,6 @@ - POST Application @@ -1138,7 +1089,6 @@ - POST Application @@ -1166,7 +1116,6 @@ - POST Application @@ -1194,7 +1143,6 @@ - POST Application @@ -1222,7 +1170,6 @@ - POST Application @@ -1242,7 +1189,6 @@ 14d 0 FLOAT - POST Application diff --git a/zabbix_templates/6.4/documentation/custom-os-linux-disk-io-details.html b/zabbix_templates/6.4/documentation/custom-os-linux-disk-io-details.html index 20c9069..c76f95a 100644 --- a/zabbix_templates/6.4/documentation/custom-os-linux-disk-io-details.html +++ b/zabbix_templates/6.4/documentation/custom-os-linux-disk-io-details.html @@ -73,7 +73,7 @@

Discovery rule "Disk IO detail discovery"

TypeZABBIX_ACTIVE -Delay +Delay60m

Trigger Overview

@@ -88,23 +88,23 @@

Graph Overview

NameElements -IO: Activitiescustom.vfs.dev.io.active[{#BLOCKDEVICE}]
custom.vfs.dev.queue_depth[{#BLOCKDEVICE}]
+{#BLOCKDEVICE} - IO: Activitiescustom.vfs.dev.io.active[{#BLOCKDEVICE}]
custom.vfs.dev.queue_depth[{#BLOCKDEVICE}]
 -IO: Merged Operationscustom.vfs.dev.read.merged[{#BLOCKDEVICE}]
custom.vfs.dev.write.merged[{#BLOCKDEVICE}]
+{#BLOCKDEVICE} - IO: Merged Operationscustom.vfs.dev.read.merged[{#BLOCKDEVICE}]
custom.vfs.dev.write.merged[{#BLOCKDEVICE}]
 -IO: Milleseconds spend in IOcustom.vfs.dev.read.ms[{#BLOCKDEVICE}]
custom.vfs.dev.write.ms[{#BLOCKDEVICE}]
custom.vfs.dev.io.ms[{#BLOCKDEVICE}]
custom.vfs.dev.weight.io.ms[{#BLOCKDEVICE}]
+{#BLOCKDEVICE} - IO: Milleseconds spend in IOcustom.vfs.dev.read.ms[{#BLOCKDEVICE}]
custom.vfs.dev.write.ms[{#BLOCKDEVICE}]
custom.vfs.dev.io.ms[{#BLOCKDEVICE}]
custom.vfs.dev.weight.io.ms[{#BLOCKDEVICE}]
 -IO: Opscustom.vfs.dev.read.ops[{#BLOCKDEVICE}]
custom.vfs.dev.write.ops[{#BLOCKDEVICE}]
+{#BLOCKDEVICE} - IO: Opscustom.vfs.dev.read.ops[{#BLOCKDEVICE}]
custom.vfs.dev.write.ops[{#BLOCKDEVICE}]
 -IO: Transfercustom.vfs.dev.read.sectors[{#BLOCKDEVICE}]
custom.vfs.dev.write.sectors[{#BLOCKDEVICE}]
+{#BLOCKDEVICE} - IO: Transfercustom.vfs.dev.read.sectors[{#BLOCKDEVICE}]
custom.vfs.dev.write.sectors[{#BLOCKDEVICE}]
 @@ -115,47 +115,47 @@

Item Overview

ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Currently Activecustom.vfs.dev.io.active[{#BLOCKDEVICE}]Number of I/Os currently in progress. -The only field that should go to zero. Incremented as requests are given to appropriate struct request_queue and decremented as they finish. +The only field that should go to zero. Incremented as requests are given to appropriate struct request_queue and decremented as they finish.14d0 -ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Milleseconds spend in IOcustom.vfs.dev.io.ms[{#BLOCKDEVICE}]Number of milliseconds spent doing I/Os. This field increases so long as field #12 (custom.vfs.dev.io.active) is nonzero. +ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Milleseconds spend in IOcustom.vfs.dev.io.ms[{#BLOCKDEVICE}]Number of milliseconds spent doing I/Os. This field increases so long as field #12 (custom.vfs.dev.io.active) is nonzero.14d0 -ZABBIX_ACTIVE{#BLOCKDEVICE} - IO:Queue Depthcustom.vfs.dev.queue_depth[{#BLOCKDEVICE}]Number of I/Os currently in progress.&#13; -The only field that should go to zero. Incremented as requests are given to appropriate struct request_queue and decremented as they finish. +ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Queue Depthcustom.vfs.dev.queue_depth[{#BLOCKDEVICE}]Number of I/Os currently in progress.&#13; +The only field that should go to zero. Incremented as requests are given to appropriate struct request_queue and decremented as they finish.14d0 ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Merged Readscustom.vfs.dev.read.merged[{#BLOCKDEVICE}]Number of reads merged. -Reads and writes which are adjacent to each other may be merged for efficiency. Thus two 4K reads may become one 8K read before it is ultimately handed to the disk, and so it will be counted (and queued) as only one I/O. This field lets you know how often this was done. +Reads and writes which are adjacent to each other may be merged for efficiency. Thus two 4K reads may become one 8K read before it is ultimately handed to the disk, and so it will be counted (and queued) as only one I/O. This field lets you know how often this was done.14d0 ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Milleseconds spend in Read IOcustom.vfs.dev.read.ms[{#BLOCKDEVICE}]Number of milliseconds spent reading. -This is the total number of milliseconds spent by all reads (as measured from __make_request() to end_that_request_last()). +This is the total number of milliseconds spent by all reads (as measured from __make_request() to end_that_request_last()).14d0 -ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Ops Readcustom.vfs.dev.read.ops[{#BLOCKDEVICE}]This is the total number of reads completed successfully. +ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Ops Readcustom.vfs.dev.read.ops[{#BLOCKDEVICE}]This is the total number of reads completed successfully.14d0 -ZABBIX_ACTIVE{#BLOCKDEVICE} - IO Transfer Readcustom.vfs.dev.read.sectors[{#BLOCKDEVICE}]This is the total number of sectors read successfully. +ZABBIX_ACTIVE{#BLOCKDEVICE} - IO Transfer Readcustom.vfs.dev.read.sectors[{#BLOCKDEVICE}]This is the total number of sectors read successfully.14d0 ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Milleseconds weighted spend in IOcustom.vfs.dev.weight.io.ms[{#BLOCKDEVICE}]Weighted number of milliseconds spent doing I/Os. -This field is incremented at each I/O start, I/O completion, I/O merge, or read of these stats by the number of I/Os in progress (field 12) times the number of milliseconds spent doing I/O since the last update of this field. This can provide an easy measure of both I/O completion time and the backlog that may be accumulating +This field is incremented at each I/O start, I/O completion, I/O merge, or read of these stats by the number of I/Os in progress (field 12) times the number of milliseconds spent doing I/O since the last update of this field. This can provide an easy measure of both I/O completion time and the backlog that may be accumulating14d0 ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Merged Writescustom.vfs.dev.write.merged[{#BLOCKDEVICE}]Number of writes merged. -Reads and writes which are adjacent to each other may be merged for efficiency. Thus two 4K reads may become one 8K read before it is ultimately handed to the disk, and so it will be counted (and queued) as only one I/O. This field lets you know how often this was done. +Reads and writes which are adjacent to each other may be merged for efficiency. Thus two 4K reads may become one 8K read before it is ultimately handed to the disk, and so it will be counted (and queued) as only one I/O. This field lets you know how often this was done.14d0 ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Milleseconds spend in Write IOcustom.vfs.dev.write.ms[{#BLOCKDEVICE}]Number of milliseconds spent writing.&#13; -This is the total number of milliseconds spent by all writes (as measured from __make_request() to end_that_request_last()). +This is the total number of milliseconds spent by all writes (as measured from __make_request() to end_that_request_last()).14d0 -ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Ops Writecustom.vfs.dev.write.ops[{#BLOCKDEVICE}]This is the total number of reads completed successfully. +ZABBIX_ACTIVE{#BLOCKDEVICE} - IO: Ops Writecustom.vfs.dev.write.ops[{#BLOCKDEVICE}]This is the total number of reads completed successfully.14d0 -ZABBIX_ACTIVE{#BLOCKDEVICE} - IO Transfer Writecustom.vfs.dev.write.sectors[{#BLOCKDEVICE}]This is the total number of sectors write successfully. +ZABBIX_ACTIVE{#BLOCKDEVICE} - IO Transfer Writecustom.vfs.dev.write.sectors[{#BLOCKDEVICE}]This is the total number of sectors write successfully.14d0