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

macro expension keep the very first last function call forever.

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Duplicate
    • Icon: Trivial Trivial
    • None
    • None
    • None
    • None

      I was in Zabbix 6.0.7 and I have face the problem ZBX-21266 when playing with html email notification.
      So I upgrade to 6.0.9 and now the problem is different.

      In the same e-mail I have define:

      <p><b>Item values:</b><br>
      				Name: <i>{ITEM.NAME1}</i><br>
      				Key: <i>{ITEM.KEY1}</i><br>
      				Value: <i>{ITEM.VALUE1}</i><br></p>
      				Value 15 minutes ago: <i>{?last(/{HOST.HOST1}/{ITEM.KEY1},#1:now-15m)}</i><br>
      				Value 30 minutes ago: <i>{?last(/{HOST.HOST1}/{ITEM.KEY1},#1:now-30m)}</i><br>
      				Value 60 minutes ago: <i>{?last(/{HOST.HOST1}/{ITEM.KEY1},#1:now-1h)}</i></p>
      				<p><b>
      

      This is working fine.

      But below I try to use:

      <p><b>Host: </b>{HOST.DNS} ({HOST.IP1})<br>
      					<b>Host description: </b>{HOST.DESCRIPTION}</p>
      					<p><b>Uptime: </b><i>{?last(/{HOST.HOST1}/system.uptime,#1)}</i></p>
      					<p><b>CPU usage:</b><br>
      					Latest value: <i>{?last(/{HOST.HOST1}/system.cpu.util[,,avg5],#1)}</i><br>
      

      But instead of getting the uptime (this was working in Zabbix 6.0.7) now it always returns the:

      {ITEM.VALUE1}

      So the call to system.uptime is not working.
      I also try with a simple:

      {?last(/{HOST.HOST1}/system.uptime)}
      

      Without success.

      So ZBX-21266 introduce a regression that prevent us from calling any other items.
      The very first one is used in every call to {$last(....)}

      Also the calls to min and max applied to the very first item retrieved and not to the one specified in the parameters.

            igorbach Igor Gorbach
            Circle Pr2
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: