[ZBX-22383] New script on action execution problem Created: 2023 Feb 20  Updated: 2023 Mar 24

Status: Confirmed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D), Frontend (F)
Affects Version/s: 6.2.7
Fix Version/s: None

Type: Problem report Priority: Major
Reporter: Evgeny Semerikov Assignee: Zabbix Development Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-02-20-14-14-09-184.png     PNG File image-2023-02-20-14-22-01-078.png    

 Description   

Hello! I'm trying to use new script execution feature and get a lot of problems.

First, I'm created a new script definition:

Second, I'm create action with this script, but have disappointed, because in action creation dialog I must chose where action must be executed, but this is defined in script creation dialog (on zabbix server)!

Third, if I use macro like ({EVENT.DATE} {EVENT.TIME}) ant try to use script in recovery action, then date and time inserts when event occurs, insted when event closed, because for this I must user another macroses ({EVENT.RECOVERY.DATE} {EVENT.RECOVERY.TIME}). Of course, this can be circumvented by adding another script, but somehow it's too much I think.



 Comments   
Comment by Edgar Akhmetshin [ 2023 Feb 22 ]

Second, I'm create action with this script, but have disappointed, because in action creation dialog I must chose where action must be executed, but this is defined in script creation dialog (on zabbix server)!

Thank you for reporting this, documentation and implementation confuses. Confirmed.

Third, if I use macro like (

Unknown macro: {EVENT.DATE}

Unknown macro: {EVENT.TIME}

) ant try to use script in recovery action, then date and time inserts when event occurs, insted when event closed, because for this I must user another macroses (

Unknown macro: {EVENT.RECOVERY.DATE}

Unknown macro: {EVENT.RECOVERY.TIME}

). Of course, this can be circumvented by adding another script, but somehow it's too much I think.

Works by design.

Generated at Tue Apr 08 01:09:41 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.