Nagios monitors potential sync issues

From: Ross Gardner
Sent: 03 October 2012 19:25
To: Ramesh Ramakrishnan
Cc: Caitlyn Duggan; Jeffrey Collemer; Autumn Francesca
Subject: Re: Bing Bids for Yell

I didn't notice any errors in the log files. I did notice entries in the db with newBids and old newBidSetDate values. This is an indication that the bids were set awhile ago and haven't been sent to Bing yet. As Caitlyn mentioned, this could be caused by sync problems. Running the bid updater with the "-t" test flag will show whether it thinks there are pending bids. If tsacommon is out-of-date then I'm guessing the searchEngineAccounts table or searchEngineUsers table might be off.

From a monitoring point of view, it might be good to set up nagios to query the db every day for old bids. Something along the lines of:
select count(1) from admaxBids where newBid is not null and newBidSetDate < '<yesterday's date maybe>';
Any result > 0 could indicate a problem.

From: Caitlyn Duggan
Sent: Wednesday, October 03, 2012 2:18 PM
To: Ramesh Ramakrishnan; Ross Gardner
Cc: Jeffrey Collemer; Autumn Francesca
Subject: RE: Bing Bids for Yell

Errors from seupdate should be looked out for. But no error is thrown from the bid updater app in this case. Basically the app looks for any bids that are ready to be sent to the search engine. It uses a query and just selects all the available bids. If a certain bid is missing necessary information (ie. searchEngineGroups.. there are others, just can't think of the tables off the top of my head), it is not considered "ready" so it does not get sent to the search engine, but there is no error shown in the logs. That would probably be a very useful enhancement. Until that is added to the code, someone should monitor the admaxBids table as Ross did today.