Zabbix randomly notifies Problem

[sbs]

I have been using Zabbix for a few years, and have am now running v6.4 in a composed environment.
I have upgraded to last stable version last week, but the problem remains.

The problem is that I receive random "problems" notification followed by "problem resolved" notification, usually, on the next poll.

Below is an example of such notification:

Problem: SERVER room is powered by UPS Battery on UPS Eaton
Problem started at 09:18:29 on 2024.02.13
Problem name: SERVER room is powered by UPS Battery on UPS Eaton

Resolved in 31s: SERVER room is powered by UPS Battery on UPS Eaton
Problem has been resolved at 09:19:00 on 2024.02.13
Problem name: SERVER room is powered by UPS Battery on UPS Eaton 
Problem duration: 31s​​

When looking at the UPS log, there is no power outage or alarm sent. This started after a scheduled power down operation on the UPS, and now continues to occur a few times a week.

When I look at the "last received" data, zabbix pretends it received the alarm information from the UPS.

How can I debug and fix this issue?

[LenR]

I guess "SERVER room is powered by UPS Battery on UPS Eaton" is a trigger? Look at the item history referenced by that trigger. One of them has a value that caused the trigger, then the item value changes and the problem is resolved.

If this doesn't get you closer, post the trigger logic.

One common issue involves nodata(). If you have an item updating (for example) every 1m, and you have nodata(1m), any slight lag in update can cause a false alarm. Always set item updates and nodata() to reasonable values, with nodata larger.

[sbs]

Hello,

The trigger logic is as follows :
last(/ups146/UPS-OutputPowerSource)=1



I reused a UPS template and adapted it a bit, since there was no template matching exactly our model. After further inquiring, zabbix, is right and the UPS is sending the notices. I may need to adjust the triggers as this alert may not be adapted to our UPS model.

Thank you for looking into this.

Regards,