Change information send in alert email body

[TcoUpLoad]

Hi,
We have VMware Cluster that has associated the VMware template that find VMs by Discover VMware VMs template. At this point i have 2 problems.
> 1st the Discover VMware VMs mas host prototype that get his IP by #VM.IP Macro but if the VM has more then 2 network cards and if the 1st was the DMZ card the VM start trigger events about Ping. Is there any way of change it that because the VMware Guest template has Network device discovery rule that only give me metrics can i get the IP and Netmask ?
> 2nd the Discover VMware VMs has a Mounted filesystem discovery that has trigger prototype called VMware: Free disk space on {#FSNAME} less 10%. When it is activated, we configure the alert triggers action to sent an email. The default body is:

Problem started at {EVENT.TIME} on {EVENT.DATE}
Problem name: {EVENT.NAME}
Host: {HOST.NAME}
Severity: {EVENT.SEVERITY}
Operational data: {EVENT.OPDATA}
Original problem ID: {EVENT.ID}​​

The real problem is EVENT.OPDATA only return a percent of free space. How can i get more information like the real free space in GB or MB?

I have zabbix 6.4.10

[TcoUpLoad]

I need to add VMware: Free disk space on {#FSNAME} e VMware: Total disk space on {#FSNAME} data to the trigger prototype so i have better info when the email is send !

[cyber]

Yes. Your event email can only contain information that is available in that trigger. You do not have info about any other item, but only those used in trigger expression.

[TcoUpLoad]

but the trigger expression is not what throw the event? if i add more expressions to the trigger, didn't it need to do more checks? That data i need are items prototypes how can i add them in the trigger expression ?

[cyber]

What else throws the event? Trigger expression defines a condition which raises "The Problem". This "rising" is the event. And also vice versa.. when trigger expression is not true anymore, "The Problem" is resolved, this is also an event..
One way to add additional data to event is to use additional items in trigger expression with somekind of condition, that does not influence result... like "... and vfs.fs.size["{#FSNAME}","pfree"] < 101" This is always true anyway, but you can now refer this item value in opdata as {ITEM.VALUE2}