Zabbix 7.0.6 Cannot Discover Windows Services

[hsyncftlk]

Hello everyone,

As I mentioned in the title, when I try to monitor my Windows servers, it cannot get the data of my Windows services by "Windows services discovery" in the current "Windows by Zabbix agent" template. In other words, no items are created and I cannot monitor. I should also mention that I can collect and monitor all server data except services.

Let me also explain a bit about my current setup; I have a Zabbix server in the central partition and I collect the data from the remote site I want to monitor via proxy. Proxy, server, agent, etc. are all version 7.0.6.

There are the following lines in the proxy logs on the remote site:
Zabbix agent item “service.discovery” on host “xxx” failed: first network error, wait for 15 seconds
resuming Zabbix agent checks on host “xxx” connection restored.

I don't think there is a network access problem because other discovery rules are working fine and I can monitor them.

Waiting for your support.

[kyus]

Check the following macros on those hosts (or template):
{$SERVICE.NAME.MATCHES}
{$SERVICE.NAME.NOT_MATCHES}

They're used to filter which services will be monitored, by default there's a bunch of services that are excluded.

[kyus]

I wrote this before reading the network error part
I won't delete it because it may be useful for someone, even though it may not be in your case...

[kyus]

Try testing the discovery rule to see if you can get any value.
Go to one of your Windows host's "Discovery rules" and click on "Windows services discovery".
Click on "Test", then in "Get value and test".

[hsyncftlk]

When I test windows services discovery, I get a connection timed out error, but with other discovery rules I can get data and the test succeeds.

I would like to add this by the way. Since this topology is a closed loop, all the ports used by default have been changed. In other words, the agent does not communicate on port 10050, but on a different port. I have adjusted this in the agent configuration as well as in the zabbix frontend. Could this be the problem?

[kyus]

If everything is configured correctly (it seems like it is, since the other items are working) the port wouldn't be an issue.
Since you are getting a timeout error, try increasing the timeout in the agent config and in the item to see if it changes anything.

[hsyncftlk]

I had previously set the timeout value to 20 in the agent, proxy and server configuration. Now I increased it to 20 on the item, but there was no change. This seems to be a very strange problem.

The Windows servers I want to monitor are running in the cloud, could this be a situation caused by my cloud service provider?

I can't think of anything else