Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-27141

Discovery override with NO_DISCOVER item does not update dependent trigger

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • None
    • 7.0.19
    • Server (S)
    • None
    • AlmaLinux 8.10 / Postgres 17

      Steps to reproduce:
      setup operations disabling discovery for items with connected trigger severity override does not work, only no_discover on matched items is set

      without NO_DISCOVER operation triggers are managed by the override rule

      overrides:

      • name: 'Disable backups monitoring for matched dbs'
        step: '1'
        filter:
        conditions:
      • macro: ' {#DBNAME}

        '
        value: '{$PG.BACKUP.FILTER.DBNAME}'
        formulaid: A
        operations:

      • operationobject: ITEM_PROTOTYPE
        operator: LIKE
        value: recent
        discover: NO_DISCOVER
      • operationobject: TRIGGER_PROTOTYPE
        operator: LIKE
        value: recent
        severity: NOT_CLASSIFIED

      Expected result:
      severity override was added to operations because 'disable not discovered' is not set to 'immediately'
      matched items should not be discovered and deleted according to 'not discovered delete policy'
      matched triggers should change severity immediately until deleted by the delete policy

            zabbix.support Zabbix Support Team
            itspief Denis Pavlov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: