All services should have oops reporting triggers

Reported by Dave Morley on 2012-04-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Developer registration portal
Low
Unassigned
Ratings and Reviews server
Low
Unassigned
Software Center Agent
Low
Unassigned
Ubuntu Apps Directory
Low
Unassigned
ubuntu-recommender
Low
Unassigned

Bug Description

In order to safely and reliably test for the various oopses we wish to require of a service we need to have a trigger for them like poison.

I'm assuming we need 403, 404, 500 suggestions on other common issues appriciated.

Dave Morley (davmor2) on 2012-04-10
Changed in developer-portal:
importance: Undecided → Low
Changed in rnr-server:
importance: Undecided → Low
Changed in software-center-agent:
importance: Undecided → Low
Changed in ubuntu-recommender:
importance: Undecided → Low
description: updated
affects: application-web-catalog → ubuntu-webcatalog
Changed in ubuntu-webcatalog:
importance: Undecided → Low
Jonathan Lange (jml) wrote :

FWIW, I think this is a nigh uncloseable bug. Partly because it's phrased as an imperative rather than as a description of a problem, but also because the imperative is open-ended.

If we don't yet know what common events should trigger OOPSes, then it's probably best to have someone figure that out before we file a bug for it.

On the specific events listed, I don't think it's a great idea to have OOPS reports for 404s, and probably not 403s. Traditional analytics tools are better for that.

Dave Morley (davmor2) on 2012-11-16
Changed in developer-portal:
status: New → Confirmed
Changed in rnr-server:
status: New → Confirmed
Changed in software-center-agent:
status: New → Confirmed
Changed in ubuntu-webcatalog:
status: New → Confirmed
Changed in ubuntu-recommender:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers