Trigger file system space remaining per drive

[Trips2007]

I am monitoring a Windows Server. It inherits the following item from Mounted filesystem discovery:

vfs.fs.size[{#FSNAME},free]

as well as this trigger:

{myhost.com:vfs.fs.size[{#FSNAME},pfree].last(0)}<20

The problem is, the OS drive (C only holds the OS and nothing else. It will always have only about 10% free space.

Other drives in the system should trigger at the 20% threshold.

Is there a straightforward mechanism to "override" the trigger threshold for C:?

If not, is the best approach to clone Template OS Windows, remove that item and trigger, and setup items and triggers specific to the individual drives that this type of server has in my environment?

[herta]

I usually just disable the trigger for that host (i.e. not the template or discovery rule) and create a new one which is more appropriate for that host.

[tchjts1]

Go to Configuration --> Hosts and look at the list of triggers. Simply disable the existing trigger and create the one you want... at the host level.

[Trips2007]

I have a bunch of hosts that all have the exact same drive configuration. Can I disable the vfs.fs.size[{#FSNAME},free] item somehow in a template those hosts share, or do I really have to click through to each host and disable it individually?

[herta]

In that case, yes, I'd copy the windows template and create my own based on that copy.

[Trips2007]

I tried following these suggestions, but unfortunately cannot redefine

vfs.fs.size[{#FSNAME},pfree]

I get the error message

Item with key "vfs.fs.size[C:\,pfree]" already exists on "myhost.com" as an item created from item prototype.

Presumably that key is already being created from file system discovery? Can I disable file system discovery for my new template?

[herta]

Odd. Having two templates using the same items should not be an issue. (I always make copies of the default templates and change my copies. That way, if I mess up, I can still revert to the original.)

Then again, if you already assigned the original template to "myhost.com", you can get conflicts.
Could you check whether "myhost.com" is still linked to the old template? If it is, unlink and clear the old template from "myhost.com". You may have to look at the "myhost.com" items, and delete what items/triggers/graphs still remain of the old template.
Then link the new template, and you should be set.