Problems triggered by Trigger Prototype remains although acknowledged and disabled

[MopedRoswitta]

Hi,

I'm currently dealing with trigger prototypes. By defaults there's one that triggers a problem when the disk space usage falls under 20%. Because that's not suitable for me I've cloned the trigger prototype and changed the value to <10 (10%). Then I've activated manual acknowledge and disabled the origin.

When I check the applied trigger prototypes per host it looks correct. The obvisious next step was to acknowledge the old problem manually.

But after a while I've checked the dashboard again and the same old problem appeared - disk usage less than 20%


What I am doing wrong?

[aigars.kadikis]

Hello, MopedRoswitta!

It is not exactly what you are asking for but please consider to use GB checking per drive (on windows) or per mount point (on linux).

https://catonrug.blogspot.com/2018/04/define-free-space-limit-on-each-mount-point-gb-mb.html

https://www.zabbix.com/documentation/3.4/manual/discovery/low_level_discovery#using_lld_macros_in_user_macro_contexts

This solution is used more in real life situations.

The whole idea is to:
1) Delete "Mounted filesystem discovery" in "Template OS Windows" and "Template OS Linux" template;
2) Create another template just for free space checking;
3) Assign template to all hosts where megabytes matter;
4) Define LOW_SPACE_LIMIT per host and per each discovered volume.

Regards,