Per filesystem per host mounted filesystem problems

[slgibnz]

Hi there.

I'm old school and have hosts with mounted filesystems that are small (they are a natural quota) and don't have 10G free.

When adding a new host it makes sense to add a default set of template triggers but I'm really find it difficult to follow the process of click here, click there, add this, add a tag (?), click there, clone the trigger, figure out some esoteric query that I can't edit, test it, apply it.

It doesn't seem possible to directly modify the current trigger dependency of say "<hostname>/<myfilesystem>: Disk space is critically low (used > {$VFS.FS.PUSED.MAX.CRIT:"/"}%)" and adjust the threshold to say 2G.
And then have it replace the condition for only that filesystem on only that host without affecting the default template list.

Rinse and repeat for the other 50 warnings that come up.

Is there a way of doing this using a CLI ? Export a trigger, edit the text, import it ?

[slgibnz]

Cheers for that. Thought so.

"fine tune it on all hosts"

Could you assist me on how to construct your own or modify specifically for a single host for a single filesystem, and how to disable the default and replace it with the amended one.

[slgibnz]

Figured out that I needed to clone one and rewrite everything for every filesystem on every host.
Some filesystems are 1GB some are 1TB.
Where is $VFS.FS.PUSED.MAX.CRIT set ?

FYI. This is a better product than Nagios or netdata.cloud but it's as bad as anything Tivoli or BMC has come up with as far as configuration goes ... every filesystem has to have 20% free ... expected to have a spare 800GB lying around at all times on a 4TB filesystem.

[cyber]

Templates are created based on "average joe".. They cannot fit everyones needs at once. Not everyone has 4T FS-es around.. You can of course create your own templates, with different trigger expressions and different values. I don't have any default templates in our system... Maybe some network stuff, but heavily modified...
Default macro is set in template, "Macros" tab.
But with comparison to BMC I have to disagree, I have not seen anything as bad as BMC ..:P Worked with BEM/BPPM infra for some years.... ugh....