Mini OOPS Tools sprint, taking place in Campinas, SP, Brazil, 20-24 September 2010.

We're discussing

• Bug 461269: oops reports should be grouped by oops signature not exception type and exception value (better grouping of oopses; better relation oopses-real problems)

• How to move this information to be easily accessible via web
• Improve oops-tools to handle queries for a given pageid

How to reduce all OOPS emails into one with grouped information

Send only one email to the list including information broke down by team:

• stats section is global, for all production instances
• each team section shows top exception and top timeout and the percentage of
  • oops reports the team is responsible comparing to the total.
    • maybe show top offending pageid (i.e. the pageid with the greates number
      • of oopses) instead?
• all team sections show link to a full team report

Subject: Oops report for 2010-09-22

= Stats for 2010-09-22 =

* 10000 Exceptions
* 50000 Time Outs


== Bugs 20 % ==
Full report: https://lp-oops.canonical.com/summary/?team=Bugs&date=2010-09-22

 * 230 ConjoinedBugTaskError: 'Foo bar is foobared'
 * 440 TimeOut: 'some broken page'

== Code 50 % ==
Full report: https://lp-oops.canonical.com/summary/?team=Code&date=2010-09-22

 * 100 TooNewRecipeError: 'recipe is foobared'
 * 1140 TimeOut: 'some broken page'


== Foundations 10 % ==
Full report: https://lp-oops.canonical.com/summary/?team=Code&date=2010-09-22

 * 330 LibrarianDiskError: 'librarian is down'
 * 666 TimeOut: 'some other page is broken'

We're doing

• Bug 540890: exclude robot posts from reports

• Bug 251896: oops-tools should filter out not found errors referred from non-local domains

We did

• Bug 612354: fix oops-tools bootstraping