Clean up Stacktrace fields in OOPS CF
Bug #1075226 reported by
Evan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Daisy |
Triaged
|
Low
|
Unassigned | ||
Bug Description
We don't ever use the Stacktrace field in the individual OOPS reports - the retraced stacktraces live in the Stacktrace column family. However, we include these not-retraced Stacktrace fields when writing the OOPS report. As we're running low on space, it would help if we removed these and filtered them out when writing the reports in the future.
| Changed in daisy: | |
| importance: | Undecided → High |
| status: | New → Triaged |
Revision history for this message
| Brian Murray (brian-murray) wrote | #1 |
| Changed in daisy: | |
| importance: | High → Low |
Revision history for this message
| Brian Murray (brian-murray) wrote | #2 |
To post a comment you must log in.
These are filtered when we are writing reports.
revno: 420
committer: Brian Murray <email address hidden>
branch nick: daisy
timestamp: Thu 2014-04-10 13:10:06 -0700
message:
daisy/submit.py: do not write ProcMaps (for python crashes), Stacktrace, and ThreadStacktrace to the OOPS CF. Additionally, remove Disassembly, ProcMaps, ProcStatus, Registers, and StacktraceTop for duplicates