to accelerate the availability of the json form of the MDSW output in ElasticSearch, I'd like to have MDSW, for a limited time, to produce both pDump and jDump. That gets the jDump into ElasticSearch immediately while the processor and Web UI can be more leisurely in moving to the new format. I'd rather not have adoption of jDump blocked by the processor and UI. The two forms of the same data could be streamed serially with a known delimiter between them ("END OF PIPE DUMP") or sent out on separate streams in parallel. Either technique could work. The new pjMDSW should have command line switch to select, pDump, jDump or both. When we want to retire the pDump, we just drop the switch on the invocation of MDSW.
This is what I want: MDSW with -m and -j switches to produce pDump and jDump respectively. If both commandline switches are present, I want pDump streamed on stdout then folllowed by a sentinel (any string on a line by itself, like "END OF PIPE DUMP") followed by the jDump.
the branch "jdump" in my github repo (https://github.com/twobraids/socorro/tree/jdump) has a version of the Socorro Processor that will add the jDump to a processed crash if MDSW returned it. I'm now blocked on getting a MDSW that'll produce both pDump and jDump
Pushed: http://hg.mozilla.org/users/tmielczarek_mozilla.com/minidump-stackwalk/rev/b99899ee43c7 The stackwalk binary in that repository now takes a --pipe option which will cause it to first spit out the existing pipe dump format followed by a single line consisting of: ====PIPE DUMP ENDS=== followed immediately by the JSON output.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target milestone doesn't really make any sense here, FWIW, this is not something that's shipping in Firefox.
You need to log in before you can comment on or make changes to this bug.