Ad Widget

Collapse

override a threshold for a discovered trigger

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nabbo
    Junior Member
    • Jun 2017
    • 1

    #1

    override a threshold for a discovered trigger

    Hi there

    I'm pretty new with zabbix and I'm trying to get quite simple monitoring (with larger scale in mind... hundreds of servers to monitor)

    So I have a Filesystem discovery rule (taken from the discovery rule bundled with Zabbix).

    Item key is :
    Code:
    vfs.fs.size[{#FSNAME},pfree]
    Works great, filesystems are discovered.

    In addition, I create corresponding trigger :
    Code:
    {Nimsoft_Linux:vfs.fs.size[{#FSNAME},pfree].last()}<20
    1st problem : if I want to override the threshold 20 for a particular FS, I just can't.

    I can solve this problem using a macro :
    Code:
    {Nimsoft_Linux:vfs.fs.size[{#FSNAME},pfree].last()}<{$DEFAULT.FILESYSTEM.SPACE_FREE.CRITICAL}
    and then set the macro at the template level and (when needed) at the host level.

    2nd problem : now all my filesystems have the same threshold for a given host.
    How can I deal with this ?

    (Note : I can't predict what the FS names will be. Some obvious like / or /boot, and (in most cases) some more random names.

    I see 2 options right now :
    1. Create the triggers "by hand" periodically, querying the database or API for "un-triggered" FS. This way the triggers are not discovered, so I can edit them one by one. But then if I want to change the general threshold... it becomes handy. Plus, I'd rather not write/maintain a script for that, if possible.
    2. Or I let the triggers to be discovered, and when I want to override one, I disable it and I create a manual equivalent with custom threshold... I don't like this one more because it can become very tricky to maintain when dealing with hundreds of servers...


    Please tell me there's an other option...

    Thanks for the great tool !
Working...