store the user's last few OOPSes somewhere

Bug #1858134 reported by Paul Collins on 2020-01-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

Quite often users report Launchpad timeouts but are unaware the the OOPS ID is needed to debug them properly. Then they reload the affected page, or perform some other action, and lose the OOPS ID forever.

It would be useful if Launchpad stored the last few OOPSes encountered by the user, along with a timestamp. and had a page we could ask the user to visit that rendered this information.

Stephan Woidowski (swoidowski) wrote :

Think this is a good idea. As the ID's differing from time to time it should be possible to have an overwatch-list of the last e. g. 10 ID's for better identification.

This is all already done in the oops microservice (internal only when I
left). What isn't present is any sort of hookup to let users query that
themselves. I think the code for that service was open sourced, though I
may be wrong :). - its a little django app. Teaching it to have a formal
API, giving that API federated auth and allowing LP to use that API for an
OOPS-view would then be fairly straight forward, no LP schema changes
needed (or desirable).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers