Service Discovery items and triggers

[yaniv.elizarov]

Hey
I have an issue with service.discovery items:

Currently I have the below defined items and triggers

Item prototypes:
Name: Template OS Windows: State of service {#SERVICE.NAME}
Key: service.info["{#SERVICE.NAME}",state]
Update interval: 30s
Show value: Windows service state
Trigger prototype expression:
{<Host>:service.info["{#SERVICE.NAME}",state].last()}<>0 and {<Host>:service.info["{#SERVICE.NAME}",startup].last()}<>3

Name: Template OS Windows: {#SERVICE.NAME} startup type is {#SERVICE.STARTUPNAME}
Key: service.info["{#SERVICE.NAME}",startup]
Update interval: 30s
Show value: Windows service startup
Trigger prototype expression:
{<Host>:service.info["{#SERVICE.NAME}",startup].min(60)}=1

As I understand it my item data should show the following for running services:
For Template OS Windows: State of service {#SERVICE.NAME}:
- 0 to show service is running
- 255 should never occur because service does exist and is running
- The graph should be stable at 0 and never go to 255 unless the service has been uninstalled

For Template OS Windows: {#SERVICE.NAME} startup type is {#SERVICE.STARTUPNAME}:
- As long as the service exists I would assume it would stay listed as existing with its startup type

In Monitoring > Latest data
My 2 issues are:

The item for service startup type returns "Cannot find the specified service"

and

The item for service state returns "running(0)" only once every 30 seconds, in the periods between I see that it returns value 255 "No such service"
This causes a saw-tooth graph between values 0 and 255.

My understanding is that the services appear in the console due to them having been discovered by Zabbix Agent
So the question that then follows is "Why is a service that is discovered by Zabbix Agent listed as 'unfound' or 'No Such Service'"

You can see also the attachments.

Regards
Yaniv

[yaniv.elizarov]

Anyone have an idea how to solve it?