The Windows services discovery template is picking up service names such as "OneSyncSvc_260e8b5e1" and checking for their existence. No such services exist on the server, so we're getting alerts stating that they don't exist. I don't know where the template gets those weird service names. I looked on the server, and I did see a service called "OneSyncSvc_2650a834b", but not one called "OneSyncSvc_260e8b5e1". At any rate, is there a way to set the template to ignore or automatically disable those services with that funky string at the end of the service name?
-
-
When using the pre-configured templates, it helps to familiarize yourself with what the template does before you apply it widely (that also includes discovery).
You don't say anything about which version of Zabbix you're using, so I can only guess that you're using 5.x with the latest templates. If that's the case, review the macros that can be tailored at the template and/or host level to exclude particular services from discovery: https://git.zabbix.com/projects/ZBX/.../windows_agent -
Thank you tim.mooney and csmall for your quick responses to my question! I really should have included the Zabbix version that we are using, which is 4.4.5, but we should be upgrading to the latest version soon. The link that csmall posted is exactly what I was looking for! I don't think our current version supports overrides. At least I haven't been able to find any place to create overrides in the version that we are using. But, like I said, we should be upgrading soon, so that information will come in very handy when we do. Thanks again to you both for the information that you posted. I will be giving it all a thorough reading before proceeding any further.Comment
Comment