Reason for Alert:
DB guys reindex once a week. To check all is well on reindex we run a transaction that uses the newly indexed data. If all goes well, wait until next week and run again. If all does not go well and Alert signals a warning, critical or down... then the actions of alert contact all necessary and DB gets fixed or reindexed.
3 separate step level Alerts: One for detecting Warning, another for Critical and one for Down. The reset for the Warning is an UP status, the reset for Critical is an UP or Warning status, and for Down it is a Critical, Warning or UP status.
Problem:
If Alert reports warning, critical or down... it has done its job, BUT... because it only runs the one time a week (a business cost decision), it is not able to reset until the following week if the condition no longer exists. In addition, if the condition is the same the following week... the alert does not trigger any actions, and the DB guys dont know there is a problem to fix, thus creating a bigger mess.
Question:
Because of the cost of business.... the Alert can only run once a week after the DB is indexed, how then does one reset the Alert in the reset logic or by some other means that will not negate future SolarWinds support?