Dynamic Report Generation

[mrowebot]

Once we have the statistics computed, we need to produce reports of these stats to show what has changed, where, and by how much.

[dantheta]

We've already got a version of change-tracking inside the database (which is done pretty cheaply). It needs a little bit of refinement, but we could do a nightly export of changes logged during the day.

The system maintains a current URL/ISP status table, which is simply the latest chronological result for a given URL/ISP. When we're updating that table, the system knows what the old and new statuses are without having to go looking for them (which would be quite expensive for the DB). It logs detected changes to another logging table for inspection. This probably needs a bit of refinement, as it is currently recording change events for errors and timeouts (which we're not really interested in). Restricted to just changes from "ok" to "blocked" and vice-versa should give a pretty useful dataset.

[mrowebot]

Exporting that data would be ideal tbh. Would you be ok with me creating an issue for that and assigning it to you?

[dantheta]

Sure, that's no problem.

On Fri, Jul 25, 2014 at 01:25:24AM -0700, Matthew Rowe wrote:

Exporting that data would be ideal tbh. Would you be ok with me creating
an issue for that and assigning it to you?

---

Reply to this email directly or view it on GitHub:
#10 (comment)