Official Windows by Zabbix agent and Windows by Zabbix agent active templates use service.discovery to discover Windows services.

Discovery rule currently filters services by:

{#SERVICE.NAME} {#SERVICE.STARTUPNAME}

Discovery data also contains the {#SERVICE.STARTUPTRIGGER} macro, which indicates whether a service is configured for Trigger Start. However, this macro is not currently used by either template (was introduced under ZBXNEXT-3493).

A service configured for Trigger Start may still have automatic or automatic delayed as its {#SERVICE.STARTUPNAME} value. Therefore, it can pass the current discovery filters and receive the following trigger prototype: {#SERVICE.NAME} {#SERVICE.STARTUPNAME}

Services configured for Trigger Start may stop as part of their normal Windows behavior. As a result, the existing trigger prototype may generate unnecessary problems when such a service remains stopped for three consecutive checks.

Suggested change

Add configurable filtering based on {#SERVICE.STARTUPTRIGGER} to the Windows service discovery rule in both templates:

• Windows by Zabbix agent
• Windows by Zabbix agent active

The filter could follow the same pattern as the existing service discovery filters:

{$SERVICE.STARTUPTRIGGER.MATCHES} = .*
{$SERVICE.STARTUPTRIGGER.NOT_MATCHES} = ^1$

By default, services where {#SERVICE.STARTUPTRIGGER} is 1 should be excluded from discovery. Users should still be able to override these macros if they want to monitor services configured for Trigger Start.