[ZBXNEXT-1645] Macros on trigger level for use in action operations Created: 2013 Mar 05  Updated: 2017 Feb 14  Resolved: 2017 Feb 14

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F), Server (S)
Affects Version/s: 2.0.5
Fix Version/s: None

Type: Change Request Priority: Minor
Reporter: Marc Assignee: Unassigned
Resolution: Duplicate Votes: 5
Labels: macros, trigger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux, CentOS-6.3, PostgreSQL 9.1.8, Apache HTTPD-2.2.15, PHP-5.3.3


Issue Links:
Duplicate
duplicates ZBXNEXT-2087 Custom fields to use and show in dash... Closed

 Description   

Would be nice to be able to set some kind of macros/variables on trigger level which then can be referenced in action operations.
That way one can provide additional information per trigger without putting them into the trigger name itself.

One use case might be the connection to another monitoring infrastructure which can handle/needs additional codes or tags. The only way to achieve this with the current release is to put such information into the trigger name what can look very ugly inside Zabbix and other actions.

 Comments   
Comment by Oleksii Zagorskyi [ 2013 Mar 06 ]

How about {TRIGGER.DESCRIPTION} macro for notifications ?
I think it should satisfy most needs in similar cases.

Comment by Marc [ 2013 Mar 06 ]

Some things are too obvious.
Oleksiy, thank you very much for this valuable hint!

Edit:
However, that work-around may lead to confusion, since it's no description.
Dedicated macros will have some advantages. Macros can be put at fixed positions within an action and their names would make it clear what information to put into them, without inspecting the action operation.

Comment by Marc [ 2013 Nov 17 ]

Another use case for this could be ZBXNEXT-2026.
Of course only if ZBXNEXT-1645 gets implemented by a fourth level of User macros (Global->Template->Host->Trigger).

Comment by Glebs Ivanovskis (Inactive) [ 2017 Feb 14 ]

With custom event tags and {EVENT.TAGS} macro added in 3.2, I guess, there is nothing more we can do here. Closing as duplicate of ZBXNEXT-2087.

Generated at Fri Apr 26 17:28:58 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.