Hi all,
I have the problem that the Windows service edgeupdate is detected as not running as is set to start automatically (delayed). I changed
Configuration -Templates - Windows services by Zabbix agent and Windows services by Zabbix agent active.
I added edgeupdate (this is the correct short serivce name) to the Macro {$SERVICE.NAME.NOT_MATCHES}.
As this did not help I also changed
Administration - General - Regular Expressions - Windows service names for discovery
and added edgeupdate to the Result is FALSE Expression.
After that I removed the serive triggers from the hosts, but they re-appear after the next service discovery. Has anybody an idea what I am missing?
Im am running Zabbix 6.2 and I am using the template Windows by Zabbix agent active.
Any help would be appreciated. I have looked into multiple posts regardings service discovery, but as far as I have read, the change of the Macro {$SERVICE.NAME.NOT_MATCHES} should do the trick.
Kind regards,
Jens
I have the problem that the Windows service edgeupdate is detected as not running as is set to start automatically (delayed). I changed
Configuration -Templates - Windows services by Zabbix agent and Windows services by Zabbix agent active.
I added edgeupdate (this is the correct short serivce name) to the Macro {$SERVICE.NAME.NOT_MATCHES}.
As this did not help I also changed
Administration - General - Regular Expressions - Windows service names for discovery
and added edgeupdate to the Result is FALSE Expression.
After that I removed the serive triggers from the hosts, but they re-appear after the next service discovery. Has anybody an idea what I am missing?
Im am running Zabbix 6.2 and I am using the template Windows by Zabbix agent active.
Any help would be appreciated. I have looked into multiple posts regardings service discovery, but as far as I have read, the change of the Macro {$SERVICE.NAME.NOT_MATCHES} should do the trick.
Kind regards,
Jens