Hello,
I ran into a problem with automatic Windows service discoveries. Let me explain:
Our environment has 4 clients (all of them running Win Server 2019) currently with zabbix agent (6.4.8.2400) installed. All 4 clients have the same config file which was built with a trial-and-error method to find out the best solution working for us. The required ports are open between the zabbix server and the clients.
I managed to apply some templates which we found useful for our scenario. This includes monitoring HDD, RAM, CPU usage. I would like to set up discovery for Windows services too. This is where the problem kicks in. So I used the default template which is configured to detect and register all services running on the server with the exception of the default exclusions. Now it is already a week since the servers were linked to the "Windows services by Zabbix agent" template, but it looks like the discovery is not working at all. I have other discovery rules in the other templates (Network interfaces discovery, Mounted filesystem discovery, Physical disk discovery) and they are working perfectly fine. After a server gets linked to any template having the appropriate discovery, it receives the data within minutes, triggers get auto added as defined by the discovery and they can be monitored from Zabbix. However, this is not the situation with the Windows services discovery.
I tried setting to log level on the clients to show extra debug information and basing on the log there is indeed some discovery done for the services.
Not the whole string, but an excerpt: JSON before sending .......:[{"host":"HOSTNAME","key":"service.discovery" -> and then a looong list of services.
Normally this feature should discover all services by default and create a trigger for each of them (which would be a bit of spamming since not everyone is interested in all default Windows services). In my case no service shows up in Zabbix interface. No triggers are created for any service for the server with the default "Windows services by Zabbix agent" template attached. Absolutely nothing. Looks like the server did not receive the data or could not properly pass it to the monitoring interface.
I also tried running the service discovery manually with the execute now option, but the results are the same: nothing happens at all.
I have no idea what could be causing the problem, because everything else seems to be working apart from the Windows service discovery.
Any advice would be appreciated!
I ran into a problem with automatic Windows service discoveries. Let me explain:
Our environment has 4 clients (all of them running Win Server 2019) currently with zabbix agent (6.4.8.2400) installed. All 4 clients have the same config file which was built with a trial-and-error method to find out the best solution working for us. The required ports are open between the zabbix server and the clients.
I managed to apply some templates which we found useful for our scenario. This includes monitoring HDD, RAM, CPU usage. I would like to set up discovery for Windows services too. This is where the problem kicks in. So I used the default template which is configured to detect and register all services running on the server with the exception of the default exclusions. Now it is already a week since the servers were linked to the "Windows services by Zabbix agent" template, but it looks like the discovery is not working at all. I have other discovery rules in the other templates (Network interfaces discovery, Mounted filesystem discovery, Physical disk discovery) and they are working perfectly fine. After a server gets linked to any template having the appropriate discovery, it receives the data within minutes, triggers get auto added as defined by the discovery and they can be monitored from Zabbix. However, this is not the situation with the Windows services discovery.
I tried setting to log level on the clients to show extra debug information and basing on the log there is indeed some discovery done for the services.
Not the whole string, but an excerpt: JSON before sending .......:[{"host":"HOSTNAME","key":"service.discovery" -> and then a looong list of services.
Normally this feature should discover all services by default and create a trigger for each of them (which would be a bit of spamming since not everyone is interested in all default Windows services). In my case no service shows up in Zabbix interface. No triggers are created for any service for the server with the default "Windows services by Zabbix agent" template attached. Absolutely nothing. Looks like the server did not receive the data or could not properly pass it to the monitoring interface.
I also tried running the service discovery manually with the execute now option, but the results are the same: nothing happens at all.
I have no idea what could be causing the problem, because everything else seems to be working apart from the Windows service discovery.
Any advice would be appreciated!
Comment