It's great that I can now guarantee that we're always monitoring our AIX filesystems without having to manually add them when someone adds a volume!
However, the triggers aren't a one size fits all across all filesystems within a template.
I may have a trigger to alert at 10% full but some might be at 5%.
In the past, I would clone the trigger from the template, customize it and disable the Template:Host trigger
How would I handle this issue now? I don't see a way to clone a trigger based off of of trigger prototype.
Also, when I do try to clone, the {#FSNAME} macro is getting carried over.. which basically creates two identical triggers.
This is the Trigger prototype that I have. {Template_AIX:vfs.fs.size[{#FSNAME},pfree].last(0)}<10
I'd want it to be something different for a particular filesystem on a specific host but not result in duplicate alerts
Brian
However, the triggers aren't a one size fits all across all filesystems within a template.
I may have a trigger to alert at 10% full but some might be at 5%.
In the past, I would clone the trigger from the template, customize it and disable the Template:Host trigger
How would I handle this issue now? I don't see a way to clone a trigger based off of of trigger prototype.
Also, when I do try to clone, the {#FSNAME} macro is getting carried over.. which basically creates two identical triggers.
This is the Trigger prototype that I have. {Template_AIX:vfs.fs.size[{#FSNAME},pfree].last(0)}<10
I'd want it to be something different for a particular filesystem on a specific host but not result in duplicate alerts
Brian
Comment