I've got a set of items and triggers that are creating a false positive. Without modifying scripts that another department owns, the only way I can see to eliminate the timing issue is to run both checks at the same time. Here's the scenario:
We have a file that is generated by our backup system, when it starts the DB.
That file gets removed, indicating that it is taking the DB down for backup
I check for that file every minute during the normal backup window, but the DB is already quiet, and comes down in less than one minute. Occasionally Zabbix will see that the DB is down before it has noticed the file has been removed, causing an alert be generated.
I don't really want to wait two checks for the DB trigger, because I don't want the DB to be down for that long of a period before I get a notice. What would be ideal is that in checking for the DB to be up, I also check for that file, at the exact same time.
Is there any way to accomplish what I'm looking for?
We have a file that is generated by our backup system, when it starts the DB.
That file gets removed, indicating that it is taking the DB down for backup
I check for that file every minute during the normal backup window, but the DB is already quiet, and comes down in less than one minute. Occasionally Zabbix will see that the DB is down before it has noticed the file has been removed, causing an alert be generated.
I don't really want to wait two checks for the DB trigger, because I don't want the DB to be down for that long of a period before I get a notice. What would be ideal is that in checking for the DB to be up, I also check for that file, at the exact same time.
Is there any way to accomplish what I'm looking for?
Comment