The User Bug Report BugButton generates a JSON document, and communicates with the User Bug Report server over HTTP. This JSON is "what's posted".
Integration make use of this JSON data, for example -- stored in whole for S3 integrations, or formatted nicely for Email integrations.
The important thing though is -- all the stuff in the JSON! User Bug Report aims to tell you everything you need to know to fix a bug without going back to your users.
This is a user defined data set -- passed in through the BugButton or ambient on
Snapshot from the browser location with all the properties about the URL, here's an example:
These are the fields filled in by the user in the bug submission form.
Data uri encoded version of the screenshot. You can use this directly in an
Dimensions for the screenshot -- the browser size when the user pushed the button.
An array of note pins users left on your screenshot.
An array of console messages captured by the browser. This can get big, but is supremely useful to see what was going on before a user hit the bug button.
This example below was captured with the wonderful Debug library which generates colored strings.
Information about the browser, from the browser. I'm using Chrome on my Mac at the moment.
Using the browser debug and profiling capability, an array of network requests. Super handy to see if your server or a server you rely on is failing you.
Or -- if it is too slow!
Knowing when from the client point of view can tell you if clock skew or time zone bugs are plaguing you.