5.58 KB, text/plain
Collector accepts anything with "ProductName" and "Version" in the collector POST, but that's not enough for processing and reporting. Let's document the actual required fields.
Created attachment 8527069 [details] grep of every use of the raw_crash within the processor code Here's a listing of _every_ use of the raw crash by the processor_2015 rule system. This is a great starting point on determining what fields are required. The "stackwalker" program itself gets to see the raw_crash. Its requirements for fields is not represented in this attachment.
The processor rules handle some information missing, so while I understand the thesis of this bug, I'm not sure it helps us a lot. Say we did document it ... yay? Should we be rejecting crashes that miss some data? Some crashes come in corrupted--should we nix those? Further, the attachment is from 3 years ago and things have changed. Given that, I think I'm going to WONTFIX this. If it turns out it's helpful, we can reopen and do it in the processor rewrite.
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.