Windows services is not running (startup type automatic delayed)

[Henryqueivanaga]

Hey guys!

I am responsible for administering Zabbix at the company where I work and I am starting to learn about the tool. I checked several ways to try to resolve the case here on the forum but I have some addendums. Could you help me, please?

I'm experiencing some Windows services issues discovered in Zabbix alerts. The definitive solution would be to disable the alert trigger, but my Supervisor didn't allow me to disable the trigger and so I still don't have a solution:







I already added |cbdhsvc_.*| in the trigger {$SERVICE.NAME.NOT_MATCHES}, but I also saw that alerts already discovered for it to be valid would need to disable the trigger so that it is not rediscovered. But as I reported, my supervisor did not allow this to be done and requested a solution.

What can I do?


Tksu all

[cyber]

OK.. you added to exception list, it should prevent future discovery of that item. If you look under hosts config (item list), do you see yellow "!" marked besides that item? And if you hover you mouse there, it should say something like "this item is not discovered any more and will be deleted in XXXX" ? What it means, that yes, your change in template works, but already present item will be monitored... what you can do, is to set (temporarily) "Keep lost resources" in discovery config to 0. It should remove all such items right away, when they are not discovered any more (next discovery run)... And after they are gone, you can set it back to some more reasonable period.

[cyber]

OK.. you added to exception list, it should prevent future discovery of that item. If you look under hosts config (item list), do you see yellow "!" marked besides that item? And if you hover you mouse there, it should say something like "this item is not discovered any more and will be deleted in XXXX" ? What it means, that yes, your change in template works, but already present item will be monitored... what you can do, is to set (temporarily) "Keep lost resources" in discovery config to 0. It should remove all such items right away, when they are not discovered any more (next discovery run)... And after they are gone, you can set it back to some more reasonable period.

[Henryqueivanaga]

@cyber


Tks, all done!