[ZBX-12189] Actions with ' Event acknowledged = Ack' Operation not working Created: 2017 May 16  Updated: 2017 May 30  Resolved: 2017 May 16

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 3.2.5
Fix Version/s: None

Type: Incident report Priority: Major
Reporter: Kyle Laauser Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: actions
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

VM CentOS 7 - Zabbix 3.2.4 (Note I picked 3.2.5 from the list above because 3.2.4 was not available)

Issue Links:
Duplicate
duplicates ZBXNEXT-18 Send an alert after trigger being ack... Closed

 Description   

A while ago (~6 months) I created an Action that would email a User Group when an event had been acknowledged. Here's the Action Configuration:
Conditions:

  • Time period in 1-7,00:00-24:00 (Note that I have tried NO Conditions as well as specifically naming a trigger - same result)
    Operations:
  • Default operation step duration: 60 (Note I have tried various ranges including 600 and 3600)
  • Steps: 1-1 (Note I have tried 1-10 and 1-0)
  • Operation Type: Send Message
  • Send to User groups: %GroupName% (Note I have tried sending to individual Users as well)
  • Send only to: Basic HTML Email (I have an SH script that send an HTML formatted email. Note I have tried Basic Email as well)
  • Default message: unchecked
  • Conditions: Event acknowledged = Ack

When I first created this Action, it worked. I am not sure if it was an OS update, a Zabbix update, or some update-unrelated change that stopped this from working, but this Action is no longer firing.

 Comments   
Comment by richlv [ 2017 May 16 ]

this is supposed to only email escalation emails if the problem is acknowledged. it is not supposed to email when the problem is acknowledged - if that's what you want, it has never worked and is being requested in ZBXNEXT-18.

if you actually want to escalate if the problem is acknowledged, the issue is likely a misconfiguration and there is no indication of a bug - please see http://zabbix.org/wiki/Getting_help for support options.

if there are new facts that show a bug in zabbix, please do reopen this issue and add that detail here.

Comment by Kyle Laauser [ 2017 May 16 ]

richlv - I am confused about your reply, given that this did work for some time.
Would a possible solution be to change the number of steps to a larger number or to change the default action time? I've done this in the past and it sort of matches up with what you're saying, but if I have too many steps in the operation, it will just continue to send the acknowledgement email until the number of steps has been reached. I'm definitely looking to just send ONE out when the Problem has been Acknowledged.
I've looked around the Zabbix wiki and also forums and haven't found anything relating to this particular setup - could you perhaps direct me to a specific page/link?

Comment by richlv [ 2017 May 16 ]

if your goal is to send out an alert when the problem is acknowledged, it has never worked as you intended - it might have some random chance to work in a remotely similar way, but not really. that's what ZBXNEXT-18 is about.

Comment by Kyle Laauser [ 2017 May 16 ]

Understood - I see that it's slated for 3.4 release but doesn't show up in the roadmap. Can you confirm?

Comment by richlv [ 2017 May 16 ]

unfortunately, zabbix team does not communicate roadmap/plans anymore, so you would have to guess based on other indicators

Comment by Kyle Laauser [ 2017 May 16 ]

Gotcha! Thanks for your clarification, richlv - it's much appreciated.

Generated at Thu Apr 25 22:22:22 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.