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

Trigger no data 22 hours for a rarely updated log item

    XMLWordPrintable

Details

    • Problem report
    • Status: Closed
    • Trivial
    • Resolution: Won't fix
    • 5.0.28
    • None
    • Server (S)
    • None
    • VM, OS Centos 8, php7.4, mysql 8.0, zabbix-server 5.0.28

    Description

      Hello!

      Steps to reproduce:

      1. Create an item analysis of the log for the presence of the text "error" ( {host:log[file.log,,,50,skip]). Update interval every 1 hour, but new text is rarely written to the log, 1 time in 3 months (if the program is successfully executed) , and if the error is in the log, then re-recording after 1 day. # Create trigger, problem expression: \{host:log[file.log,,,50,skip].str(error)}

        =1

      2. Recovery expression to close the issue if there are no errors in the last 22 hours: {host:log[file.log,,,50,skip].nodata(22h)}=1 or {host:log[file.log,,, 50,skip].str(error,22h)}=0

      Result:
      But for some reason, the restore trigger does not close after 22 hours or more, when nothing new is written in the log. 

      Expected:
      Issue will close after 22 hours when there is no new log item data.
      What could be the reason? The nodata function has a time limit?

      Attachments

        Activity

          People

            zabbix.support Zabbix Support Team
            anyqov Alexey
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: