Send structured errors through telemetry

[KyleAMathews]

Currently gatsby-telemetry sends a JSON string for errors.

This makes it difficult to identify what are reoccurring errors that Gatsby users are seeing.

To fix this, we should analyze errors and structure them before sending them off.

We can also enhance errors with more information e.g. at what point in the Gatsby lifecycle did the error happen? What plugin (if any) throw the error, etc.

This will be a good first step towards implementing structured error reporting gatsbyjs/rfcs#37

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contributefor more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[jamo]

I believe this has been implemented already