Problems with windows server process monitoring.

[u1875]

Hello!
I live in Japan and I am using zabbix to monitor the server.
The following events occurred the other day, so please let me know.

Windows process monitoring
service_state
Although we are doing it, the specific process will have the status of "255".

■ Environment
· Zabbix server
Ver: 3.0
OS: CentOS 7
· Zabbix agent
Ver: 3.0
OS: Windows2012R2

■ Process name to be checked
· Keyserver
· Keyserver 2

■ A problem
When we check the process status with wind sc query command
Both of the above processes are in operation status,
In zabbix, one process has a status of 255,
It is a situation that the service can not be found.

■ Question matter
1. Please teach if the cause is known.
2. Can you teach if there are matters to be carried out, items to be confirmed?

■ Confirmation items
1. Process check on the server side
Execute the "sc query" command on the server.
· Keyserver
STATE: RUNNING
· Keyserver 2
STATE: RUNNING

2. Status at item "service_state" of zabbix
· Keyserver
Status: 0
· Keyserver 2
Status: 255

3. Status in the item "service.info" of zabbix
· Keyserver
Status: 0
· Keyserver 2
Status: 255

4. Acquisition of service list using item "services" of zabbix
· Keyserver
Listed
· Keyserver 2
Not on the list

Sorry to trouble you, but I would appreciate it if you could get wisdom.
Thank you.

[aigars.kadikis]

On server 3.0 there is already built-in functionality for checking windows service state. Use function service.info[].

There are a bunch state codes available to compare like:
0 - running
1 - paused
2 - start pending
3 - pause pending
4 - continue pending
5 - stop pending
6 - stopped
7 - unknown
255 - no such service;

Here is how you create item key:

And the trigger expression would look similar to this:

{hostname:service.info[Spooler,state].min(#3)}<>0

Best regards,