Hi all,
We are running into an issue where we are getting alerts during a reboot for older log entries. It appears that the nodata check seems to be somehow losing its spot between reboots of servers, and as a result the following trigger is sending alerts for old log entries it has already alerted on previously.
Here's the action in question we are having trouble with. Edited to get around the "Too many links" filter:
log hardware_failures nodata 300 = 0
Is there a configuration option we are missing somewhere, or a change to the trigger that can be made so that it keeps it's history between reboots and doesn't alert on old log entries?
We are running into an issue where we are getting alerts during a reboot for older log entries. It appears that the nodata check seems to be somehow losing its spot between reboots of servers, and as a result the following trigger is sending alerts for old log entries it has already alerted on previously.
Here's the action in question we are having trouble with. Edited to get around the "Too many links" filter:
log hardware_failures nodata 300 = 0
Is there a configuration option we are missing somewhere, or a change to the trigger that can be made so that it keeps it's history between reboots and doesn't alert on old log entries?