Hi Folks,
I've got zabbix set up to watch the alert log of an Oracle database. Now that database ran out of space to put his redologs, which caused it to have a fairly mild case of log-diarrhea, causing the trigger looking for 'ORA-' in the log to fire many times. This in turn caused a huge wave of zabbix spam in a mailbox.... Obviously, that's not what I want.
How can I have this set so the trigger only fires the action once, or maybe once an hour (or certain period of time), eventhough the fresh log entries may cause it to fire repeatedly?
I've been looking at the escalations but frankly I don't see if that would fix things for me, since basically the trigger is fired repeatedly, due to matching lines being written to the log repeatedly by Oracle...
I've got zabbix set up to watch the alert log of an Oracle database. Now that database ran out of space to put his redologs, which caused it to have a fairly mild case of log-diarrhea, causing the trigger looking for 'ORA-' in the log to fire many times. This in turn caused a huge wave of zabbix spam in a mailbox.... Obviously, that's not what I want.
How can I have this set so the trigger only fires the action once, or maybe once an hour (or certain period of time), eventhough the fresh log entries may cause it to fire repeatedly?
I've been looking at the escalations but frankly I don't see if that would fix things for me, since basically the trigger is fired repeatedly, due to matching lines being written to the log repeatedly by Oracle...
) for more detail - depending on your situation any (or a combination) of those solutions might help
Comment