When I configure macro context in template for disk ussage in trigger prototype like:

{Template OS Windows:vfs.fs.size[{#FSNAME},pused].last(0)}>{$LIMIT_DISK_PFILLED_HIGH:"{#FSNAME}"}

and define macro on template level like:
{$LIMIT_DISK_PFILLED_HIGH} = 95
It works well, exactly as supposed. If I redefine macro at host level for one of disk drive like:
{$LIMIT_DISK_PFILLED_HIGH:C:} = 97
Graph is displayed as supposed. - picture C_OK.png

But if I use more macro contexts at Host level like:
{$LIMIT_DISK_PFILLED_HIGH:E:} = 98
{$LIMIT_DISK_PFILLED_HIGH:C:} = 97
Graph for Disk C: is with bad trigger value and OK for Disk E.

• pictures C_BAD1png,E_OK.png

If I add macro for disk F:
{$LIMIT_DISK_PFILLED_HIGH:F:} = 99
then Graphs for disk C: and E: are with bad trigger value.

• picture E_BAD.png

It looks like evaluation of trigger values in graphs with macro context works only for the last one macro context. The others are in default macro level without context. But as I wrote before, trigger evaluation of macro context works well.

Alois Zadrazžil