867314 - modify collector to accept raven.js crashes

Status: RESOLVED FIXED

(Socorro Graveyard :: Bixie, defect)

Description

[Lonnen :lonnen]

Once we know what raven.js crashes look like, we can modify the collectors to accept them.

Comment 1

[K Lars Lohn [:lars] [:klohn]]

the current collector accepts an http POST of the fields of a crash.  From those fields, it creates a mapping object that is json serializable.  Any FILE fields within the post are treated as binary blobs and stored separately under the name of the fields of their origin.  The collector has no dependencies on the presence of any particular fields within the mapping. If the raven.js crash data is submitted in a similar manner, it is unlikely that any changes will be needed in the collector. 

What is the mechanism of the sending of raven.js crashes to a collector?

Comment 2

[Lonnen :lonnen]

Raven.js GETs a json blob to `BASE_URI/api/PROJECT_ID/store/`, where ALL_CAPS is a config value in the client. The url structure I knew was wonky, but the verb was completely unexpected.

It uses GET instead of POST to overcome CORS restrictions [1]. GET is not semantically correct, but it may actually be the better option. POST requires adding some complexity to the collectors, and requires two requests (an OPTION and then a POST) to satisfy CORS restrictions. It also means forking Raven.js to implement.


[1] https://github.com/getsentry/raven-js/issues/58

Comment 3

[K Lars Lohn [:lars] [:klohn]]

1st cut at the bixie collector can be found here:

https://github.com/mozilla/socorro/pull/1302

Comment 4

[[github robot]]

Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/6bbdbf9e4f6fbd91ac977afcb47772382dde2bfc
Merge pull request #1302 from twobraids/bixie_collector

Fixes bug 867314: added bixie collector with tests