[vtadmin-web] Add client-side error handling interface + Bugsnag implementation

[doeg]

Signed-off-by: Sara Bee [email protected]

Description

• Adds a generic + extensible interface for observability into client-side errors.
• Implements the ErrorHandler interface for Bugsnag, for deployments that use it.

Implementations for other monitoring services (common ones being Sentry, Rollbar, Datadog, etc.) are left as future enhancements. 😸 (I briefly considered implementing one other, to prove the concept, but... it didn't really make sense to add an integration that no one uses!) I looked into the JavaScript libraries for the aforementioned monitoring services and all of them fit nicely into the ErrorHandler interface proposed here.

Also unimplemented for now + worth mentioning are sourcemaps, which provide proper stack-traces for errors (since our client-side code is minified). "Undocumented" is perhaps a better term than "unimplemented", as source map uploads will (unfortunately) be the responsibility of the operator. I do promise to document how we do it, once we do it. 🙏

Here's an example of what this (specifically, the metadata) looks like in Bugsnag:

And here's what it looks like with the Bugsnag/Slack integration:

Many thanks to David + Anders from PlanetScale for pointing me at https://vitess.io/docs/user-guides/configuration-basic/monitoring/#tools, which was super useful in terms of precedent + documentation!

Related Issue(s)

N/A

Checklist

• Tests were added or are not required
• Documentation was added or is not required

Deployment Notes

For any deployments that want to integrate VTAdmin with Bugsnag, you'll need to set the REACT_APP_BUGSNAG_API_KEY environment variable.

[doeg]

Unfortunately this diff looks much worse than it is, since I had to surround everything in a try/catch. Logic changes here are minimal and well-tested. 🙏

[ajm188]

🐛 🐍