[#ZBX-25244] Built-in {PROXY.NAME} doesn't work when using Proxy Group

[ZBX-25244] Built-in {PROXY.NAME} doesn't work when using Proxy Group Created: 2024 Sep 16 Updated: 2025 Mar 18 Resolved: 2025 Feb 07
Status:	Closed
Project:	ZABBIX BUGS AND ISSUES
Component/s:	Server (S)
Affects Version/s:	7.0.3
Fix Version/s:	7.0.10rc1, 7.2.4rc1, 7.4.0alpha1

Type:

Problem report

Priority:

Minor

Reporter:

Dawid Mos

Assignee:

Aleksejs Sestakovs

Resolution:

Fixed

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

Zabbix Server 7.0.3 with group of HA proxies (two).

Attachments:

image-2024-09-16-18-17-22-743.png

Issue Links:

Duplicate

Team:

Team B

Sprint:

DOC S25-W2/3

Story Points:

0.5

Description

Steps to reproduce:

Create group of proxies and monitor some host with it
Monitored host should have some Trigger, Action that is being fired by this Trigger and E-Mail media type with Template containing {PROXY.NAME} in message ie. message body
When Trigger is raised and Action is taken you got notification with empty {PROXY.NAME} field

Result:
See example screenshot

Expected:

{PROXY.NAME}

should contain actual Proxy server being used to monitor this host (one from the Proxy Group the Host is currently assigned to)

Additionally would be nice to introduce new built-in macro like {PROXYGROUP.NAME} containing HA Proxy Group name to fill the gap.

Comments

Comment by Dawid Mos [ 2024 Sep 16 ]

In title it has to be {PROXY.NAME}. Sorry for this mistake but I cannot edit it.

Comment by Aleksejs Sestakovs [ 2025 Feb 04 ]

Available in versions:

Generated at Tue Apr 01 13:28:04 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.