Please consider adding functionality to the Windows and Linux templates to selectively suppress disk space triggers via macro, similarly to what is implemented for network interfaces.

Example: current implementation for network interfaces:

In the "Template OS Linux" or "Template OS Windows" template, there's a trigger:

Interface {#IFNAME}({HOST.NAME}): Link down

This trigger contains:

• Problem expression:

  {TEMPLATE:item.last()}=2 and {$IFCONTROL:"{#IFNAME}"}=1

  Meaning the trigger fires only if the interface is active (controlled).

• Recovery expression:

  {TEMPLATE:item.last()}=1 or {$IFCONTROL:"{#IFNAME}"}=0

  So the trigger is cleared either when the link is back up or when control is disabled via macro.

This allows flexible trigger management without disabling item collection.

Suggested implementation for disk space:

For disk usage triggers such as: 

/mnt/backup: Disk space is critically low (used > {$VFS.FS.PUSED.MAX.CRIT:"/mnt/backup"}%)

Propose the following:

• Problem expression:

  .... and {$FSCONTROL:"{#FSNAME}"}=1

• Recovery expression:

  .... or {$FSCONTROL:"{#FSNAME}"}=0

This would enable defining host-level macros like:

{$FSCONTROL:"/mnt/backup"}=0

or

{$FSCONTROL:"D:"}=0

to suppress trigger activation for specific filesystems while keeping monitoring active.
 

Thank you for considering this enhancement.