I need help yet again!  :) 

I have another situation!  We just ran into an issue where our server is showing that there is no issue but in actuality we have a critical job that failed. 

Here is what is going on: 

- We have a Critical job that fails at 10 pm.  The status of that MSSQL monitor is Critical/RED.  (This is perfect)  NOTE: AppManager see the status as a "failed"

- At 6am AppManager POLLS the MSSQL server and finds no SQL job information. The  job status does NOT exist and is Blank "--".  The status of that MSSQL monitor now becomes Green and that job is marked as successful. 

Now in reality the job has still not run successful (STILL FAILED) but the history of the job is cleared on the SQL based on some time bases. (which we can not control)  The next time the job runs at 10pm and fails again we'll see it in AppManager for the period before SQL clears its logs. 

QUESTION?:

--How can this be avoided?

--Is there a way to ignore the status if there is NO actual status polled by AppManager?

Please me, these false positives are taking away the credibility of our server monitoring! :( 

Thanks,

Steve