[ZBX-12276] Action status showing "Failures" indefinitely and no way to reset it Created: 2017 Jun 13  Updated: 2019 Dec 10

Status: Reopened
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 3.2.6
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Ilya Kruchinin Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: actions, frontend, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 8, Zabbix packages from official repositories.

Attachments: PNG File image-2019-08-16-14-43-57-711.png     PNG File zabbix-no-media.png    
Issue Links:
Duplicate
duplicates ZBX-11612 Misleading numbers next to the status... Closed

 Description   

On "Problems" and in "Last 20 issues" widget on the main page, the "Actions" column will show red "Failures" status indefinitely if at least one alert notification has ever failed (for example, due to "no media defined" for a user).

There is no way to reset/clean this status (other than remove the user and re-create it again). New successful alert notifications (after a media is defined, for example) won't clear up this status.

 Comments   
Comment by Volker Fröhlich [ 2017 Jun 13 ]

How is that a problem or what would a reset do?

Comment by Ilya Kruchinin [ 2017 Jun 13 ]

If the root cause was fixed - why should Zabbix indefinitely show "Failures"?
This is distracting. At least an "acknowledgement" or "reset" should be there.

Otherwise - I see "Failures" every time and need to check if it's a new failure or the one that was already taken care of.

Comment by Alexander Vladishev [ 2017 Jun 14 ]

Closed as duplicate of ZBX-11612.

Comment by Ilya Kruchinin [ 2017 Jun 15 ]

Alexander, it's not a duplicate.
ZBX-11612 talks about misleading numbers, when the number of actions under the "Failure" state actually represents the number of all messages.
In this particular bug report (ZBX-12276) I'm talking about a different issue. Once all the problems with "Actions" have been fixed, it would still forever/indefinitely display the "Failure" state,
regardless of the fact that all the latest notifications went through perfectly fine. And there is no way to clear this state (misleading "Failures" message although the issues that resulted in those have long been fixed).
Please reopen.

I'd suggest something like an "ACK" button for failed "Actions" to ensure they no longer permanently affect the shown status. Alternatively, simply adding logic that checks the status of LATEST "problem/recovery" actions only to determine and show the status. This can be done in addition to things discussed in ZBX-11612, if necessary.

Comment by Ilya Kruchinin [ 2017 Jun 15 ]

Reopened.

Alexander, could you please update the problem description so that it's more descriptive to ensure it is clear that it's different from ZBX-11612 (I cannot do this - no rights). I mean adding a proposal for some kind of mechanism (ACK or logic tracking latest notifications only) to ensure old failures can be disregarded so that the status is displayed as "Success"

Comment by Simon Begin [ 2019 Aug 16 ]

Hi,

May I suggest a change in behaviour ?

It is that an action to send an email should NOT be a failure when the user having no media defined.

This way we could see a real notification failure when there is effectively one, for example when tried to send a SMS or Email but without success.

We do have users that want emails and others in the same group that don't, so we have no way to solve this and we allways see red "Failures" in our dashboard.

I think this will answers a few similar problems.

Generated at Sun Apr 06 23:59:02 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.