Hello Oleg,

Yes, when you configure the things in the Web Front-end - you change those in the database directly. But Zabbix Server daemon reloads the Configuration cache once in a minute(by the default). So your value will be updated with the expected only not earlier than the next configuration cache.

It is not a bug - this is by design, that Front-end and Server daemon are communicating through the database, not directly.

Further reading Zabbix overview & config file for Zabbix Server.

Regards,
Aleksejs!

Hi,

Thank you for clarification on configuration cache. However, this does not explain different behaviour for Calculated type and, for instance, Zabbix agent or SNMP agent types. If I create another item with Zabbix agent type it gets updated with expected intervals both on Items page and Last data page.

Let me know if I need to elaborate the issue.

Thanks.

Sorry, could you please create some screenshots and detailed steps on how to reproduce the issue?

Hi,

Thanks for looking into it. I created test template zbx_export_templates.xml

^{UserParameter line:}

^{UserParameter=unixtime.discovery,/etc/zabbix/externalscripts/ZBX-14661.sample}

^{Discovery script:}

1. cat /etc/zabbix/externalscripts/ZBX-14661.sample
   #!/bin/sh
   DATE=`/bin/date +%s`
   echo "{ \"data\":["
   echo "{"
   echo "\"{#ITEM_NAME}\":\"UNIXTIME\","
   echo "\"{#ITEM_VALUE}\":\"$DATE\""
   echo "}"
   echo "]}"

^{Set CacheUpdateFrequency=120 to be able to catch the difference in output.}

^{Screenshots attached. You could see on ZBX-14661_last_value that Last check is getting updated each 10 seconds but Last value only with interval set up in CacheUpdateFrequency.}

^{Hope this makes this clear. Let me know if you need more info.}

^Thanks.

At the same time, the Formula field in Monitoring > Hosts > Items follows "Update interval" for that item prototype and gets updated accordingly.

Actually, it follows Update interval of discovery rule.

In order to see effect of your changes to item prototype configuration in discovered item configuration you need to wait until server/proxy executes LLD rule once again (and proxy sends LLD JSON to server).

In order to see effect of your changes to item prototype configuration in discovered item values you need to wait until server/proxy executes LLD rule once again (and proxy sends LLD JSON to server) plus until server reloads configuration from DB or new configuration gets sent to proxy.

I guess this is where confusion comes from.

Hi,

That makes sense now. Thank you for detailed explanation.

Issue may be closed.