Creating triggers for discovered services

[Gijs007]

We currently use the Windows Service discovery which automatically generates warning triggers for all services.

I'd like to make a disaster trigger for services with a certain name (which is auto discovered).
Since this service is auto discovered it doesn't have a item in the template, so every time I try to add the trigger I get the following error:
Incorrect item key "service.info[TCA2ServiceMan,state]" provided for trigger expression on "Template OS Windows".

When we try to add the service as a item to the Template OS WIndows it tells us that it's already discovered on some hosts which use this template. So we can't add the item to the Windows template..

Only option seems to roll out this trigger manually for every host..
How do we resolve this situation?

[tcilmo]

We currently use the Windows Service discovery which automatically generates warning triggers for all services.

I'd like to make a disaster trigger for services with a certain name (which is auto discovered).
Since this service is auto discovered it doesn't have a item in the template, so every time I try to add the trigger I get the following error:
Incorrect item key "service.info[TCA2ServiceMan,state]" provided for trigger expression on "Template OS Windows".

When we try to add the service as a item to the Template OS WIndows it tells us that it's already discovered on some hosts which use this template. So we can't add the item to the Windows template..

Only option seems to roll out this trigger manually for every host..
How do we resolve this situation?

Create a "trigger prototype" on the template that has your discovery rule.

Your expression would like this: {App Microsoft SQL 2016:service_state[MSSQLSERVER].last(0)}>0 and {App Microsoft SQL 2016:service_state[MSSQLSERVER].last()}<>255. The trigger won't fire if the services does not exist on a box.