Closed Bug 1511022 Opened 7 years ago Closed 7 years ago

verbose logging for signature generation

Categories

(Socorro :: Signature, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

Details

Attachments

(1 file)

Signature generation is complicated. In cases where it produces a signature that's unhelpful, it really helps to know the minutia of what happened during signature generation. Was there a sentinel? Was it looking at the right thread? Which frames did it skip? And so on. This bug covers reworking signature generation so that it logs what it did to build a signature and spits out that information in "socorro-cmd signature" in some --verbose mode.
I'd like to have this. It's helpful on a regular basis. Making it a P2.
Priority: -- → P2
Commits pushed to master at https://github.com/mozilla-services/socorro https://github.com/mozilla-services/socorro/commit/adf96a111c4b39234b72b037923abc7b74b46aae bug 1511022: rework signature generation to use a Result instance This reworks signature generation to use a Result instance that gets passed from rule to rule. The Result class has some helper methods for manipulating the signature and keeping track of what happened during generation. This will make it easier to debug. https://github.com/mozilla-services/socorro/commit/57cccb801cbdb2852e752767656658eefc8a4a90 fix bug 1511022: add debug logging for signature generation This adds debug logging for signature generation specifically around irrelevant, prefix, and sentinal related events. This will make it a lot easier to see how changes to the siglists files affect things. https://github.com/mozilla-services/socorro/commit/eca53436c68e003a16aaa724567210df77bee58c Merge pull request #4749 from willkg/1511022-sig-logging fix bug 1511022: better signature generation debug logging
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: