python-oops-tools

new topics are not included in reports

Bug #658863 reported by Robert Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-oops-tools
Triaged
High
Unassigned

Bug Description

we now have oops from the librarian and codebrowse, and more appservers; AIUI the OOPS reports are manually grouped.

We should instead report *all* oopses from *any* prefix in the 'lpnet' summary - its fine to have other more focused summaries, but we should have a catchall that:
 - gets everything
 - folk interested in overall status can look at.

Diogo Matsubara (matsubara)
Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Diogo Matsubara (matsubara) wrote :

The way I'd like to have this fixed is a complement to the fix for bug 667375. Once we eliminate the manual step needed to update summaries to find out new prefixes, we should be able to easily have a catch all summary (this bug is also related to bug 652351)

Revision history for this message
Robert Collins (lifeless) wrote :

I'd like to have *one* summary for all production services and unknown prefixes should turn up in it: we shouldn't need to consult two reports to see all oopses.

Robert Collins (lifeless)
summary: - oops reports should automatically include new oops prefixes
+ new topics are not included in reports
Revision history for this message
Robert Collins (lifeless) wrote :

Should be straightforward: add a default report to the config somewhere, check that when a new topic is found.

tags: added: easy
William Grant (wgrant)
affects: launchpad → python-oops-tools
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.