[ZBXNEXT-5255] Add support for trigger and event macros in global scripts Created: 2019 Jun 04 Updated: 2021 Oct 18 Resolved: 2021 Sep 25 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F), Server (S) |
| Affects Version/s: | 4.0.8 |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Major |
| Reporter: | Ramivis Exi | Assignee: | Valdis Murzins |
| Resolution: | Fixed | Votes: | 11 |
| Labels: | events, globalscripts, macros | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Currently, just host macro are supported in global script, but I need use triggers and events macro too for specific actions when the script run.. {EVENT.NAME}, {EVENT.DATE}, {TRIGGER.SEVERITY}, etc. Its possible? |
| Comments |
| Comment by Stephen Courtney [ 2019 Oct 24 ] |
|
Our specific use-case for this would be to use the {EVENT.TAGS} macro in a global script, - this would allow us to start a Windows service that had stopped (using a trigger action is not suitable, as there will be times when we don't want a service to automatically be restarted). |
| Comment by Jose Lourdes [ 2019 Nov 03 ] |
|
This feature would bring so many benefits to us. This would allow us to start a Windows service that had stopped. In our case, instead of 1st Line support teams get in touch with 2nd Line support teams, they would have a means to start the services, because the don´t have access to servers. Using a trigger action is not suitable. |
| Comment by Ramivis Exi [ 2020 May 13 ] |
|
is there any prevision for release of the feature? Tks |
| Comment by Frank Geister [ 2020 Jun 26 ] |
|
Hi, same here it would be a great benefit for us also. I added a similar request: https://support.zabbix.com/browse/ZBXNEXT-6029
Background we need an option to "manually" trigger our CreateIncident.pl script which creates an Incident from the selected event. Therfore to get data from the event to handover to Service Manager like user who opened the incident (thankfully is available since 5.0.2 and it's working) and we need the event data. We need at least the {EVENT.ID} to query additional data from the RestAPI to enrich the Incident within global script to get additional data (occurence, message, system name etc.) from the event. Please can you check if it is possible to implement? Many thanks! |
| Comment by Frank Geister [ 2020 Jun 26 ] |
|
We currently evaluating if Zabbix could be a replacement for our current Monitoring solution (BMC Patrol). The most pain point we got is that it is not possible to handover any type of MACROS or ITEM values ({{$HOST.HOST}:<KEY>}) to global script as argument which can be triggered manually by our operators in a event/problem context. Like described above, the {EVENT.ID} will be at least the argument we need to query additional data from the specific event where the operator executes the remote script from to query additional information by RestAPI from this specific event for our Incident creation intefrace. Would be awesome if you can provide this in a future release.
Many thanks. |
| Comment by Stefan [ 2020 Aug 10 ] |
|
Would be great to get it integrated. Thanks in advance. |
| Comment by Ramivis Exi [ 2021 Feb 24 ] |
|
Hello guys, is a very important feature, do you know when it will be available? maybe in version 5.4 or 6.0? =) |
| Comment by Andris Mednis [ 2021 Feb 24 ] |
|
I hope you will get something with |
| Comment by Ramivis Exi [ 2021 Sep 25 ] |
|
thank you, solved in version 5.4 |