For JavaScript
ErrorDock for JavaScript.
ErrorDock captures uncaught exceptions and unhandled promise rejections in browser applications, resolves minified stack traces through uploaded source maps, and records the breadcrumb trail of navigation, network and console activity leading up to each error.
Minified traces resolved to your source
Upload each source map for its release to the artifacts endpoint, with a server key that has the artifacts:write scope, and stack frames resolve to original file, line and column. A trace pointing at bundle.min.js:1:48210 is not a debugging aid. During the beta, source-map upload is enabled per organisation.
Breadcrumbs from the browser
Navigation, fetch and XHR calls, console output and user interactions are recorded as breadcrumbs, so an error arrives with the sequence that produced it.
Small by design
The browser SDK is kept deliberately small and loads asynchronously. A monitoring tool that measurably degrades the performance it reports on is self-defeating.
Related
- ErrorDock for React. Error boundaries, component stacks and feature usage tracking for React applications, from one SDK.
- Find the failure. Keep the context. Group exceptions into issues, inspect stack traces and breadcrumbs, and understand which users and releases are affected.
- What is error monitoring? Error monitoring is the practice of automatically capturing, grouping and prioritising exceptions from running software. A practical guide to how it works.
Bring your application into focus.
Tell us about your stack. We will help define the right beta setup for your first project.