We are running zabbix 2.2.1 and taking advantage of some of the new housekeeper features. We previously had issues with our events table growing too large, impacting database performance (mysql), the events housekeeper has helped substantially here. We housekeep events > 7 days.
However, we see that events are getting deleted even for triggers that are still in a problem state. These problem triggers > 7 days can no longer clear on their own since their events are gone, so our only option (that I know of) has been to update the triggers table, and set triggers with value = 1 (Problem) to value = 0 (OK) older than 7 days, then any "problems" that still exist will come back with a new event / problem trigger. Our NOC has to be prepped for this so they can record already known problem triggers, so when the trigger reappears they arent spinning up incidents etc.
Does anyone have a better work around for this? Is there something we should be doing differently with event housekeeper to prevent this? Would this be considered a bug I should open a report on?
Thanks in advance.
However, we see that events are getting deleted even for triggers that are still in a problem state. These problem triggers > 7 days can no longer clear on their own since their events are gone, so our only option (that I know of) has been to update the triggers table, and set triggers with value = 1 (Problem) to value = 0 (OK) older than 7 days, then any "problems" that still exist will come back with a new event / problem trigger. Our NOC has to be prepped for this so they can record already known problem triggers, so when the trigger reappears they arent spinning up incidents etc.
Does anyone have a better work around for this? Is there something we should be doing differently with event housekeeper to prevent this? Would this be considered a bug I should open a report on?
Thanks in advance.
Comment