This holiday season I'm going to take time to review the top 10 blog posts, as measured by hits per post, and offer new information in some way so you get something out of it too!
The first post we're going to review is "Purging concurrent and Fixed Assets" from 2/1/13 with 60 views.
While I had already created the alert before putting up the blog post, I learned something afterwards by having our team act upon the alert: it is possible to CREATE a problem instead of resolve one taking action. The alert was created to look at problems when the Calculate Gains and Losses or Depreciation Run concurrent reports error in the Concurrent Manager within the past 2 hours, but it does NOT require action to be taken in our example since we don't run into problems until we get close to the request getting purged within 3 DAYS time. I've seen a few times when we clear out fa_book_controls.mass_request_id too quickly it seems to cause some issues.
The lesson to take away from this is, building alerts is great as long as they are followed with clear documentation and make sense 100% of the time. If an alert goes off too much, or gives a false positive, you are setting yourself up for failure eventually.