On 01/10/09 at 20:08 +0200, Sandro Tosi wrote: > Package: qa.debian.org > Severity: wishlist > User: qa.debian....@packages.debian.org > Usertags: udd > > Hi! > It's common in a datawarehouse system (like UDD can be considered) to keep > track > of the update jobs times: start, end, duration, records elaborated and so on. > > This will allow to query such information to generate a report ob jobs > executions like: durations (mean, stddev, etc), growth, performance, eventual > tuning due to interaction with other scripts, and so no. > > Such information, are usually stored in a different (internal) schema than the > main one, but I think we can just add a table in 'udd' (maybe prefixed with > 'udd_' to claryfy it's a UDD interal information table) for such information.
Hi Sandro, Timestamps are now exported to http://udd.debian.org/timing.txt , but this doesn't keep historical information. A patch adding the table you describe would be appreciated (the code would have to be python) -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
