Hyper-V, Centos 7.4, Zabbix 3.4.2

Hello Len,
thanks for the reporting. Could you please attach a screenshot of you action log for this message? Feel free to hide all sensitive information.

Regards,
Aleksejs!

Hopefully, 2 screen shots

So this isn't a bug actually, because you are using the {PROXY.NAME1} which utilizes number as an items identifier. In case of Auto-registration - there is no any item to identify. You need to use {PROXY.NAME} or {PROXY.DESCRIPTION} without any number and this should work fine.

More information: https://www.zabbix.com/documentation/3.4/manual/appendix/macros/supported_by_location

I'm closing the issue. Thank you!

Regards,
Aleksejs!

We copied the message text from our production 2.4 system, so it must have changed somewhere along the way.

In the olden days in contexts where macro indexes had no meaning indexed macros were resolved to the same thing as non-indexed macros (in your example {PROXY.NAME1} used to be the same as {PROXY.NAME}, {PROXY.NAME5} or {PROXY.NAME9}). This was changed in ZBX-9729 (so nowadays only {PROXY.NAME} is resolved, but {PROXY.NAME5} or {PROXY.NAME9} are not recognized).

You can find more details if you read Upgrade notes carefully.

If this should work, the documentation is confusing:

{PROXY.NAME<1-9>}
Notifications and commands, Internal notifications
Proxy name of the Nth item in the trigger expression that caused a notification. Supported since 1.8.4.

There is no indication of this use case, while on the other hand:

{HOST.HOST<1-9>}
..., Auto registration notifications, ...

glebs.ivanovskis Good point, actually. Would you be so kind to create documentation ticket for that? I fear that if I do it myself it will be assigned to me and I will have to figure out what's what and I don't really want to.

Can you please fix the typo in the issue title?

glebs.ivanovskis Done. Thank you for noticing!