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

Allow "system.localtime" metric be collected in active mode

    XMLWordPrintable

Details

    • Problem report
    • Status: Doc. sign-off
    • Trivial
    • Resolution: Unresolved
    • 4.0.3
    • None
    • Agent (G), Server (S)
    • None
    • Team B
    • Sprint 58 (Nov 2019), Sprint 59 (Dec 2019), Sprint 60 (Jan 2020), Sprint 61 (Feb 2020), Sprint 62 (Mar 2020), Sprint 63 (Apr 2020), Sprint 64 (May 2020), Sprint 65 (Jun 2020), Sprint 66 (Jul 2020), Sprint 67 (Aug 2020), Sprint 68 (Sep 2020), Sprint 69 (Oct 2020), Sprint 70 (Nov 2020), Sprint 71 (Dec 2020), Sprint 72 (Jan 2021), Sprint 73 (Feb 2021), Sprint 74 (Mar 2021), Sprint 75 (Apr 2021), Sprint 76 (May 2021), Sprint 77 (Jun 2021), Sprint 78 (Jul 2021), Sprint 79 (Aug 2021), Sprint 80 (Sep 2021), Sprint 81 (Oct 2021)
    • 0

    Description

      Glebs Ivanovskis in this comment describes how Zabbix server processes the fuzzytime() function at the moment. The key moment is: the current value of item is compared with timestamp of this value. As result, it makes useless trigger expressions like "host:system.localtime.fuzzytime(SomeValue)" if this metric is collected by agent in active mode, as value and timestamp should be equal "by design" in this case.

      At the same time, documentation always has the following description for trigger function fuzzytime():

      Checking how much an item value (as timestamp) differs from the Zabbix server time.

      Key moment: "differs from the Zabbix server time" but anything else (including value's timestamp)!

      I believe that the behaviour of this trigger function should be modified according to documentation. In result, we could use this metric by active-mode agents, too.

      I understand that it could cause to some problems (for example, false positives if some values have been buffered and delayed by active-mode agents and intermediate proxies), but these problems much more predictable and understandable than the current behaviour. The possibility to monitor time deviation using the standard active-mode agent is another very important reason.

      Attachments

        1. corrected.png
          corrected.png
          17 kB
        2. simple.png
          simple.png
          12 kB
        3. timestamp_correction.png
          timestamp_correction.png
          14 kB
        4. zbx_export_hosts.xml
          7 kB

        Issue Links

          Activity

            People

              asestakovs Aleksejs Sestakovs
              constantin.oshmyan Constantin Oshmyan
              Votes:
              14 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated: