Ad Widget

Collapse

Splitting disk read/write await trigger prototype in Linux Agent by Zabbix ?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Pigi_102
    Member
    • Sep 2021
    • 35

    #1

    Splitting disk read/write await trigger prototype in Linux Agent by Zabbix ?

    Hi all,
    I know, the subject sound strange but I've been asked to specialize the trigger and dividing it in two: one for read and one for write.
    Actually the prototype states ( in expression ):
    Code:
    min(/Linux block devices by Zabbix agent/vfs.dev.read.await[{#DEVNAME}],15m) > {$VFS.DEV.READ.AWAIT.WARN:"{#DEVNAME}"} or min(/Linux block devices by Zabbix agent/vfs.dev.write.await[{#DEVNAME}],15m) > {$VFS.DEV.WRITE.AWAIT.WARN:"{#DEVNAME}"}
    And his name is :
    Code:
    {#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)
    Splitting by itself seems an easy task:
    Clone, remove the read part on one and remove the write part on the other, and same for the name to keep it uniq.

    My question is that I dont' understand how the trigger relate to the item prototype and what I'm supposed to do once I make this modification.
    Would be enough to wiait until the lld run again and I get the two different triggers ? Or I do need to do something more ?

    Thanks all in advance
Working...