Calculated items in discovery template become 'not supported' - need a delay?

[BrentN]

Consider the following calculated item in a low level discovery for file systems:

Calculate free space:
last("vfs.fs.size[{#FSNAME},total]") - last("vfs.fs.size[{#FSNAME},used]")

Now, I realize I could just query the agent directly for this value, but I'm trying to minimize the number of checks being performed. I already know the total and used for a volume, getting free is a simple calculation.

The problem is that it takes a few cycles for the active agent to fully discover and populate the items required for the calculation. The item is getting marked as not supported because there is no last value for those items when it runs the first time.

Any way around this?

[ccreamer]

I noticed this as well. I have set up a php or a .sh file on the monitored server that I run under crontab that grabs the info I want. I then push it to the zabbix server using the monitored server's instance of zabbix_sender. I change the item type from zabbix agent to zabbix trapper.

It's allot of work in the beginning. I certainly wish that the zabbix agent checks were not so time sensitive. Luckily I work in a virtualized environment and I am able to script out the new builds from template servers where I already have my zabbix scripts configured.

[richlv]

The problem is that it takes a few cycles for the active agent to fully discover and populate the items required for the calculation. The item is getting marked as not supported because there is no last value for those items when it runs the first time.

Any way around this?

while some complicated logic could be added, does the temporary unsupported state cause any serious issues for you ?
it does resolve automatically after a while, right ?

[aaronchu]

I'm also having this issue. My calculated item doesn't seem to come out of 'unsupported' by itself. When would it do so, if it ever does?

[Zaniwoop]

I also have this problem.
The calculated items NEVER come out of [NOT SUPPORTED] mode

[jfroot]

Sorry to revive an old post.. but has there been any fixes for this? Running 2.0.4 and using calculated items in LLD templates. They will constantly flap to unsupported saying "cannot evaluate function ... not found." Then it will usually correct itself, but not always.

[BrentN]

I've just set up a 2.0.6 install to retest a number of issues that previously prevented us from switching to Zabbix and it looks like this still happens.

[rakesh456]

I have also noticed this as well. I have set up a PHP or a.sh file on the monitored server, which I have run under a crontab that grabs the information I want. Thereafter, I push it to the Zabbix server by using the monitored server to the instance of Zabbix sender. I also made a change to the item type from the Zabbix agent to the Zabbix trapper. Best Pichwai paintings online website is also hosted on Zabbix server.
It will be having a lot of work in the beginning and certainly, I wish to the Zabbix agent who checks the results were not so time-sensitive. Luck is that I work in a virtualized surroundings and I can able to script the new builds from template servers, where I already have my Zabbix scripts configured.

Thank you.