Greetings Zabbix community!
We have prod/stage/dev environment. We want to disable ""Processor load is too high" trigger on stage/dev environment and leave it on prod servers. To make this happen we full cloned Default Windows/Linux templates. From the template we deleted the following trigger.
After disabling it, we added the stage/dev servers to be monitored using by this new Customized template which has "Processor load is too high" trigger deleted. However, we are still getting alerts for "Processor load is too high", even though it is linked to new customized template. I have restarted zabbix-proxy as well as agent services on the host. Did not help. The other thing is that when I check at the host level the "processor load" trigger is still there. The servers were already in zabbix and monitored by default template. Not sure if that caused that trigger stay there. I know that we can disable/delete at the each host level, but we are looking for the solution to modify the global template, that way all the hosts monitored by that will have processor load disabled. We do not want to change the default template since our prod servers still going to use that template and have "Processor load" trigger enabled. So my questions are: How can I make my custom template work? Why am I still seeing processor load trigger at the host level? For the newly configured zabbix clients how/where can I configure so it gets picked up by customized template not the default template? I hope it is clear.
Any advice greatly appreciated.
We have prod/stage/dev environment. We want to disable ""Processor load is too high" trigger on stage/dev environment and leave it on prod servers. To make this happen we full cloned Default Windows/Linux templates. From the template we deleted the following trigger.
| Processor load is too high on {HOST.NAME} | {Template OS Windows:system.cpu.load[percpu,avg1].avg(5m)}>5 |
After disabling it, we added the stage/dev servers to be monitored using by this new Customized template which has "Processor load is too high" trigger deleted. However, we are still getting alerts for "Processor load is too high", even though it is linked to new customized template. I have restarted zabbix-proxy as well as agent services on the host. Did not help. The other thing is that when I check at the host level the "processor load" trigger is still there. The servers were already in zabbix and monitored by default template. Not sure if that caused that trigger stay there. I know that we can disable/delete at the each host level, but we are looking for the solution to modify the global template, that way all the hosts monitored by that will have processor load disabled. We do not want to change the default template since our prod servers still going to use that template and have "Processor load" trigger enabled. So my questions are: How can I make my custom template work? Why am I still seeing processor load trigger at the host level? For the newly configured zabbix clients how/where can I configure so it gets picked up by customized template not the default template? I hope it is clear.
Any advice greatly appreciated.