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

Discovery Trigger Overrides add additional matching for item prototypes using item key

XMLWordPrintable

    • Icon: New Feature Request New Feature Request
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • None
    • 5.4.7
    • Frontend (F)
    • None
    • Zabbix 5.4.4

      Discovery overrides work as expected, for example you can add a condition for 'item prototype' and exclude the item from being discovered based on matching the item name.

      However it can be even more powerful and flexible if the item key was also able to be matched against.

      The example I have supplied is with the IF-MIB interface monitoring, where low capacity interfaces required the low capacity counters and high capacity interfaces require the high capacity counters.

      I have attached some examples of how I have had to go about it and examples of how I would like to go about it.

      At this point because the matching is only able to match against the item name and not the key I am forced to put something in the name that differentiates between the two items (i.e. HighCapacity and LowCapacity) so that it can be matched.

      I would prefer to use the same name for each item and a different key (as per examples) as the intent or what the item collects is the same regardless of the different item key used i.e. TX Bits /sec is the same regardless whether I use IF-MIB.ifEntry.ifOutOctets or IF-MIB.ifXEntry.ifHCOutOctets.

            vmurzins Valdis Murzins
            james.cook000@gmail.com James Cook
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: