Clear Events so they no longer apppear in the Dashboard

[ggiesen]

Is there any way to clear an event so it no longer appears in the Dashboard? Specifically, I have a template configured for ImemRomID to generate an informational event, but I'd like to be able to clear it. It appears as soon as I add a new device, I'm not able to get rid of it once I've seen it (ideally, by acknowledging it). How would I go about doing this?

Pasted output from my dashboard:

DEVICE1 lmemRomID on DEVICE1 has Changed 10 Feb 12:20:57 2h 6m 53s No
-
DEVICE2 lmemRomID on DEVICE2 has Changed 03 Feb 10:55:58 7d 3h 31m Yes

DEVICE3 lmemRomID on DEVICE3 has Changed 03 Feb 10:55:57 7d 3h 31m Yes
-

[froztbyte]

Is there any way to clear an event so it no longer appears in the Dashboard? Specifically, I have a template configured for ImemRomID to generate an informational event, but I'd like to be able to clear it. It appears as soon as I add a new device, I'm not able to get rid of it once I've seen it (ideally, by acknowledging it). How would I go about doing this?
...

Similar issue on my side. I'm monitoring a Cisco device with SNMP and got a line card added, now imemRomID is alerting. It's been acknowledged, but it doesn't go away (as with all events). I've tried disabling and re-enabling the item, but this doesn't make Zabbix override its internal record of the initial state of information for the specific item and then the alert comes back up at the time of the next checks. Is there any way to force Zabbix to update this or have it happen automatically?

[auro]

Hi guys!

Same problem here.

Nobody knows how to aknowledge these events?

"lmemRomID on RTR1 has Changed"
"lmemRomID on RTR2 has Changed"

The devices are identical Cisco 2611 devices.

Thanks in advance!

[jgerry]

We have similar issues on some informational items. The primary issue is, I think, that Zabbix triggers have two states, and there's no manual way to reset the state of a trigger. So every time we get an informational alert -- say, /etc/passwd has changed -- the trigger status gets reset from its normal state (FALSE) to TRUE. At some point it's set back to FALSE, but I can't find any information on how long that takes, and there's no manual way to reset the trigger.

Every one of these "informational" events generates two separate events, which I find annoying... One for when the trigger is tripped, and another when it clears. Unfortunately, there seems to be no standard time by which the trigger status resets. It's totally random as far as I can tell.

Example: I have four events that occurred on the same day. Two changes to /etc/passwd. I get four events. Check the times that those events clear. One takes 19 minutes to clear, the next takes 9 minutes.

PROBLEM: 2009.Oct.01 15:54:50 /etc/passwd has been changed on server XXX
CLEARED: 2009.Oct.01 16:13:53 /etc/passwd has been changed on server XXX

PROBLEM: 2009.Oct.01 14:34:24 /etc/passwd has been changed on server XXX
CLEARED: 2009.Oct.01 14:43:50 /etc/passwd has been changed on server XXX

At the very least, I'd like a class of events that automatically resets the trigger status immediately. Not every event needs a stateful status, but Zabbix treats every trigger as a state that needs to somehow be cleared. But, there's no manual way to clear anything.

What I'd really like to see: I think Zabbix needs a form of trigger that's not stateful, that's a one-time informational event. I also think Zabbix desperately needs a simple way to manually reset the status of any trigger.

[mlange]

I think this will be addressed with 1.8 when flexible dashboards are coming (hopefully).

[auro]

Bump!

Nobody knows how to reset these annoying cisco "lmemRomID changed" status (1.6)?

[froztbyte]

Bump!

Nobody knows how to reset these annoying cisco "lmemRomID changed" status (1.6)?

At the moment the "solution" is to disable/remove the item in question. I'm busy pulling 1.8 into our build now, will see how much has ... improved ... since 1.6.

[auro]

Tks froztbyte!
I am sure that 1.8 will kick some asses
[]s