I'm sorry if this has already been covered; I've spent some time searching, but have yet to find anything on my specific problem.
I have 400 servers, and each server has a P: (pagefile) disk.
I have a mounted filesystem LLD rule using the vfs.fs.discovery key
I have trigger prototypes for the rule, which use macros instead of numbers, so I can then override the value at host level, i.e; {Template OS Windows:vfs.fs.size[{#FSNAME},pfree].last(0)}<{DISK_CRITICAL_ALERT}
The question is, how can I ensure that by default, the P: drive has a different trigger value to the other disks?
I can obviously clone the trigger after discovery, modify it, and disable the original trigger, but I want this to happen autonomously (plus I can't see how to do this on mass, so it would take ages!)
Is there a way I can create a trigger prototype that will specifically target the P: drive, giving it a different value to the other disks discovered on each host? Or is it just a case of cloning the triggers each time I add a new host?
Appreciate your help!
I have 400 servers, and each server has a P: (pagefile) disk.
I have a mounted filesystem LLD rule using the vfs.fs.discovery key
I have trigger prototypes for the rule, which use macros instead of numbers, so I can then override the value at host level, i.e; {Template OS Windows:vfs.fs.size[{#FSNAME},pfree].last(0)}<{DISK_CRITICAL_ALERT}
The question is, how can I ensure that by default, the P: drive has a different trigger value to the other disks?
I can obviously clone the trigger after discovery, modify it, and disable the original trigger, but I want this to happen autonomously (plus I can't see how to do this on mass, so it would take ages!)
Is there a way I can create a trigger prototype that will specifically target the P: drive, giving it a different value to the other disks discovered on each host? Or is it just a case of cloning the triggers each time I add a new host?
Appreciate your help!