Hello,

I would like to configure a trigger for Windows Services where I could insert the current state name of the service.

Under the context of LLD (Key: service.discovery), when inserting the macro {#SERVICE.STATENAME} (or any others) in the name of the trigger, the macro value is only updated when the "Update interval" of the LLD is executed.
If it's 3600sec, the trigger name will display "running" (for exemple) for an hour while the service is actually down.
And even if I reduce this time (but I don't want and you know why ^^) to match the refresh cycle of the item, when the alert arise, the email notification is often wrong on the status of the service.

What I want is that the trigger name displays and changes the "Current Status" value on the fly and being human readable.

I can actually do that, change the value on the fly with the current state of the service using the variable "{ITEM.LASTVALUE1-9}", but the values that are displayed are the "numbers" that the zabbix agent generates depending on the service's state.
See : ProblemView.PNG

So my request is :
Is it possible that you add a "param" called "statename" to the "service.info[]" key ?
Only the param "state" is actually available.

So, I could create a trigger where I will compare the current state with the string "running" and raise an alarm with the "{ITEM.LASTVALUE2}" in the name that reflect the real status of the service.
See: TriggerProto.PNG