Open ajrbyers opened 9 years ago
Maintenance of the site being checked or of the checker itself? If it's maintenance of the checker itself, perhaps we ought to shoot for the stars and say "this program will never stop checking" and then figure out ways to ensure it doesn't ...
I (personally) have this user story I need to live by:
as an system admin running the monitor I need the logic that does the checking to fail rarely, if ever because the data being collected may be subject to auditing and intense scrutiny
Of the site being checked! It's a fairly common feature. Very useful for reporting % uptime as maintenance dleant cour. I think the decoupling of the check for the app means that we'll have a very limited downtime window for mondroid itself...
oh ok - hadn't considered that.
I'm thinking we collect all the data, ups or downs, good or bad, and then allow windows to be created. The datasets used to generate the uptime percentage (and latency) could then have all data from that window (optionally) filtered out.
Alerts would need to take this window into consideration.
That as reporting uptime rather than deleting uptime, edited to reflect :)
This seems like a big feature that will make reporting more complex. Can we brain dump a list of tasks to be done before we start work on it?
Let's have a chat on Friday about this.
Sure. Off the top of my head:
Allow user to add Maintenance windows. If a check falls within a maintenance window some form of notification should be displayed.