Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-4204

Zabbix should be capable to watch filesystem events

    XMLWordPrintable

Details

    • New Feature Request
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Agent (G)
    • None
    • Linux

    Description

      It would be good to have a new variant of active items:

      Instead of cyclic updates, zabbix-agent should be capable to watch inotify events on directories or files. If a inotify event appears the item(s) should be fetched and delivered.
      For some types of items this eases reviews of values/certain situations, allows to write easy nodata triggers and saves lots of space in the database.

      Example:
      The puppet state file /var/lib/puppet/state/last_run_summary.yaml is written after every puppetrun. If the zabbix detects the change and send only values if the event appear it would be easy to get the exact execution time and the resulting value of puppetruns.

      Probably it would be a good idea to have a more general solution:
      External checks which are allowed to block forever until values are delivered.

      #!/bin/bash

      inotifywait -e modify /var/lib/puppet/state/last_run_summary.yaml

      1. converted from yaml file
        echo < EOF
        Linux DB1" db.ping 1
        "Linux DB3" db.ping 0
        "Zabbix server" db.status 0
        "Zabbix server" db.error "Linux DB3 down"
        EOF

      https://openquery.com.au/blog/tool-day-inotify

      Attachments

        Activity

          People

            Unassigned Unassigned
            scoopex Marc Schoechlin
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: