Bugs with acknowledgements

[dreas]

Hi all. We're monitoring a fairly large amount of servers with Zabbix. Whenever a trigger is activated, one of our monitoring people reports the problem to our engineers and acknowledges the trigger with a specific ID related to the report so it's easy to track the progress. When the issue is fixed, the trigger auto-unacknowledges.

Now this all works in theory but there appear to be some bugs in Zabbix related to the acknowledging. We have many triggers showing "acknowledged" in tr_status.php, however we have no way to find the acknowledgement description or to remove the acknowledgement. In the Overview.php those same triggers are NOT acknowledged.

Does anyone have a patch to fix acknowledged triggers that are not really acknowledged and somehow lost their description?

Please let me know if I should provide any additional details or if things are unclear. Because of these problems it's impossible for us to keep a good overview and I really don't want to switch to another monitoring platform.

We're running 1.8.5.

[dreas]

I understand there are different acknowledges for Events and Triggers. If I look in the database for such problematic acknowledged trigger (that is not showing as such in the overview) I get:

MariaDB [zabbix]> select * from triggers where triggerid='28936';
+-----------+--------------+--------------------------------+-----+--------+-------+----------+------------+-----------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------+------------+------+
| triggerid | expression   | description                    | url | status | value | priority | lastchange | dep_level | comments                                                                                                                                                                          | error | templateid | type |
+-----------+--------------+--------------------------------+-----+--------+-------+----------+------------+-----------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------+------------+------+
|     28936 | {24232769}#0 | Trigger {HOSTNAME} |     |      0 |     1 |        3 | 1307363304 |         0 | Description |       |      15090 |    0 |
+-----------+--------------+--------------------------------+-----+--------+-------+----------+------------+-----------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------+------------+------+
1 row in set (0.00 sec)

MariaDB [zabbix]>

Is this indeed the table where this is somehow wrongly stored? The acknowledges table only seems to relate to events.

[dreas]

I guess that MySQL info is irrelevant. Anyone that can point me towards a fix?

[ghoz]

I think you should filla bug request to http://support.zabbix.com

[dreas]

Yes, good point. I thought a colleague already did that but now heard not the same case.

Maybe someone can help clarify first how things should be. Acknowledgments appear to ALWAYS relate to an event, not a trigger. zabbix.acknowledges contains all data about acknowledgments then I guess. Is this so far correct?

Now at tr_status.php there is a small "+" icon on the left of the trigger. Clicking that roles out the events, and the acknowledgment description that belongs to the event.

A lot acknowledged triggers indeed have such a "+" icon and the acknowledge message. Those all show as "Acknowledged" in the overview.php as well. Now some triggers are listed as "acknowledged" but do NOT have the "+" icon. in overview.php they don't show as acknowledged. I am unable to find any reference in the database.

Can it be that if the event is expired from the history, the acknowledgement information is lost and therefore it doesn't show the acknowledgement in overview.php (which then is a bug?) whilst remaining acknowledged in the tr_status.php (without the historical evidence)?

Any suggestions how I can clear such bad entries from the database until it's fixed in the code?

[dreas]

Attached a screenshot to make things more visual. You can see that all the top triggers are showing "acknowledged" but are missing the "+" icon on the left. These all don't show as acknowledged in the overview.

[dreas]

Looking at the events table, there are no entries <Jul 6. That's where the issues seem to start. So I presume the housekeeper deleted the event with the required information. Now I still need to find WHERE it's wrongly storing that the trigger is acknowledged.

[dreas]

Our housekeeper is indeed set to delete events after 7 days. I guess that creates orphaned acknowledgments. When then event is deleted, I presume the acknowledgement should also be deleted somehow?

[dreas]

I've opened: https://support.zabbix.com/browse/ZBX-3949