1439193 - Include a list of extensions in collected error reports

Status: NEW

(Firefox :: General, enhancement, P3)

Description

[Kris Maglione [:kmag]]

When Sentry error reports contain errors caused by extensions, it's hard to tell which extensions are responsible for those errors.

To improve the situation, we should include a list of active extensions, and also mangle stack traces to use the extension's internal ID rather than its instance ID, so stacks are the same across all users.

Comment 1

[Kris Maglione [:kmag]]

Attachment: Bug 1439193: Include extension metadata in error reports.

Review commit: https://reviewboard.mozilla.org/r/221218/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/221218/

Comment 2

[Osmose [:osmose, :mkelly]]

Can you split this patch into separate bugs for including active extensions and mangling the stack traces? The stack trace stuff seems fine, but including the active extensions will probably need a privacy review and some changes to the SUMO page if we decide to go forward with it.

Comment 3

[Osmose [:osmose, :mkelly]]

I filed bug 1441366 for the traceback-mangling specifically, and added a patch. We can keep this bug for adding the list of extensions (which may be a moot thing to need separated anyway depending on how rweiss responds to my question).

Comment 4

[Panos Astithas (he/him) [:past] (please ni?)]

Calling it P3 to get it off my triage list.

Comment 5

[Osmose [:osmose, :mkelly]]

Comment on attachment 8951953 [details]
Bug 1439193: Include extension metadata in error reports.

This patch is stale now that bug 1441366 is resolved. 

Do we still think having the list of add-ons would be useful now that we have code for stack traces and add-on ids in filenames?

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee is inactive on Bugzilla, so the assignee is being reset.