Triggers, operational data and vfs.fs.size

[Thomas Roesen]

Hi forum

We're using Zabbix 5.4 disk monitoring (C:, D:, E: etc.)

We have tried using {vfs.fs.size[C:,total]} {vfs.fs.size[C:,free]} {vfs.fs.size[C:,used]} etc. as "operational data", but they are not processed.

However, if we use the operators {ITEM.LASTVALUE3} {ITEM.LASTVALUE2} they are processed just fine.

Why can't we use the "vfs.fs.size" in the operational data? Am i missing something?

Best regards,
// Thomas, Denmark

[cyber]

You cannot use item keys in opdata... You need to use macros representing data, what is used in your trigger.

[Thomas Roesen]

Thanks for your reply.

I found this forum post:
https://www.zabbix.com/forum/zabbix-...tion-templates

Sancho writes the following:

{{HOST.HOST}:system.cpu.util[,,avg1].last()}

He seems to be using system.cpu metrics in his trigger-mail - is this not possible in operational data at all?
Can't we show "percent free" in operational data if it's not used in our trigger-expression?

Best regards,
// Thomas

[cyber]

That link points to some kind of add on, which is not even available any more and I cannot really guess, how it worked...

In OpData you can use macros, mixed with arbitrary words. But they all refer to the data already used in expression.
Supported macros are: {HOST.HOST}, {HOST.NAME}, {HOST.PORT}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {ITEM.VALUE}, {ITEM.LASTVALUE}, {ITEM.LOG.*} and {$MACRO} user macros. You cannot do any additional math with different items.

https://www.zabbix.com/documentation...iggers/trigger

[Thomas Roesen]

Ok - Thank you!