How do rules for Concurrent Manager Daily Uptime and Monthly Uptime work? (89155)

There are rules for Concurrent Manager Daily Uptime and Monthly Uptime. How do they work?

For example if the rule for Monthly Uptime fires, is that based on a calendar month or a 30-day moving window?

With the Daily Uptime does it get evaluated at a specific time of day or does it look backwards at the past 24 hours?

Monthly runs once a month and check the last full month. I.e. if ran today, it would check January 2012 uptime.
Daily runs once a day and check the uptime of yesterday. I.e. if ran today, it would report on uptime for Feb 5th.

I did notice a minor concern with both based on the way they were implemented. They are designed to only run the check once a month or once a day, respectively. The last run time (LAST_RUN_DATE) is maintained in the monitored DB in the QUEST_FG_OEBS_UPTIME_REP_MONTH and QUEST_FG_OEBS_UPTIME_REP_DAILY rows of the QUEST_FG_OEBS_PERIODIC_RUNS table. The problem is if the first time it runs is on the 25th of the month, then for the next month, it wouldn't check until the 25th of that month, when you most likely want to check on the 1st or 2nd of the month. Similarly for daily, you would want to check in the early morning, i.e. 1am, but if the last run was at 8pm, it wouldn't check again until 8pm.

So you might want to take a look at that table and possibly update those fields to the first of the month and early in the day.