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

Unneeded use of JS in template "Memory utilization"

XMLWordPrintable

    • Sprint 64 (May 2020), Sprint 65 (Jun 2020)
    • 0.25

      in the memory template for "Memory utilization" the option vm.memory.size[pavailable] is used to calculate the % free memory and in preprocessing JS is used to calculate the % in use. why not just use pused instead of pavailable with JS ?

      this is complicating readability of this trigger a lot

      {TEMPLATE_NAME:vm.memory.size[pavailable].min(5m)} >{$MEMORY.UTIL.MAX}
      

      as one would think that 10% free memory over 5min needs to be bigger then 90 to fire off the trigger and this makes no sence of course. So it took me some time to figure out what was the catch.

      https://github.com/zabbix/zabbix/tree/master/templates/os/linux_active

      also for passive

        1. pavailable-with-js.png
          pavailable-with-js.png
          11 kB
        2. pavailable.png
          pavailable.png
          10 kB
        3. pavailable.png
          pavailable.png
          10 kB
        4. 2.png
          2.png
          19 kB
        5. 1.png
          1.png
          32 kB

            tuskov Tikhon Uskov (Inactive)
            patrik patrik uytterhoeven
            Team INT
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: