ZABBIX BUGS AND ISSUES
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-10510

period condition in action configuration does not use event time

    Details

      Description

      according to documentation, period condition in action uses event time, but check_time_period() uses current time in check_action_contitions()

      2 Conditions

      Time period

      in - event time is within the time period.
      not in - event time is not within the time period.

        Activity

        Hide
        Oleksiy Zagorskyi added a comment - - edited

        Usually the time period condition is evaluated right after (escalator wakes up every 3 seconds) an event has been created.
        I don't see problems here.

        Do you have some specific use case where it causes any problem?

        Kodai Terashima Action condition is evaluated by history syncer or timer process, then start escalation if the condition matches generated event. It think that action condition should use event time as described in the documentation.

        Oleksiy Zagorskyi Got it, thank you.

        Show
        Oleksiy Zagorskyi added a comment - - edited Usually the time period condition is evaluated right after (escalator wakes up every 3 seconds) an event has been created. I don't see problems here. Do you have some specific use case where it causes any problem? Kodai Terashima Action condition is evaluated by history syncer or timer process, then start escalation if the condition matches generated event. It think that action condition should use event time as described in the documentation. Oleksiy Zagorskyi Got it, thank you.
        Hide
        Kazuo Ito added a comment -

        Action condition

        • Time period not in 1-7,00:00-01:00
        • Trigger value = PROBLEM

        Generated events 00:59:59

        process_actions is reading the actions table by the number of events.
        In the case of the following cases...

        • A lot of the event was generated
        • A lot of action has been registered
        • DB performance has deteriorated

        Execution of check_action_contitions() <- 1:00 later

        Show
        Kazuo Ito added a comment - Action condition Time period not in 1-7,00:00-01:00 Trigger value = PROBLEM Generated events 00:59:59 process_actions is reading the actions table by the number of events. In the case of the following cases... A lot of the event was generated A lot of action has been registered DB performance has deteriorated Execution of check_action_contitions() <- 1:00 later
        Hide
        Alexei Vladishev added a comment -

        Zabbix must use event time as described in the documentation. It is clearly a problem that needs to be fixed.

        Show
        Alexei Vladishev added a comment - Zabbix must use event time as described in the documentation. It is clearly a problem that needs to be fixed.
        Hide
        Viktors Tjarve added a comment - - edited

        Is it possible to provide the server log file from the occurrence of this issue?

        Kim Jongkwon OK. Please check the attached file.

        Viktors Tjarve Thanks.

        Show
        Viktors Tjarve added a comment - - edited Is it possible to provide the server log file from the occurrence of this issue? Kim Jongkwon OK. Please check the attached file. Viktors Tjarve Thanks.
        Hide
        Viktors Tjarve added a comment -

        Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-10510

        Show
        Viktors Tjarve added a comment - Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-10510
        Hide
        Andris Zeila added a comment -

        Successfully tested

        Show
        Andris Zeila added a comment - Successfully tested
        Hide
        Viktors Tjarve added a comment - - edited

        Released in:

        • 2.2.12rc1 r59226
        • 2.4.8rc1 r59227
        • 3.0.2rc1 r59229
        • 3.1.0 r59230
        Show
        Viktors Tjarve added a comment - - edited Released in: 2.2.12rc1 r59226 2.4.8rc1 r59227 3.0.2rc1 r59229 3.1.0 r59230

          People

          • Assignee:
            Unassigned
            Reporter:
            Kazuo Ito
          • Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: