For web apps
ErrorDock for web applications.
ErrorDock takes telemetry from both sides of a web application into one project. Browser errors, sessions and spans come from the browser SDK; on the server, OpenTelemetry spans join the same trace, so a slow fetch and the server work behind it read as one trace rather than two systems reconciled by timestamp.
One request, both ends
Add traceHeaders() to your fetch calls and the server's OpenTelemetry spans join the browser trace. Trace headers are added by you, call by call, rather than injected automatically.
Performance across the boundary
Browser spans from the SDK with tracing switched on and server spans from OpenTelemetry land in the same trace, so it is possible to tell a slow endpoint from slow work in the browser.
Related
- ErrorDock for JavaScript. Browser error monitoring with source map support, breadcrumbs and session context from one lightweight SDK.
- ErrorDock for ASP.NET Core. Add ErrorDock to an ASP.NET Core application in two lines for exception capture with request context, and export OpenTelemetry spans for endpoint latency percentiles and Entity Framework Core queries.
- Find the work behind the wait. Explore transaction timing and trace waterfalls alongside errors, sessions and releases, so you can investigate slow application paths with context.
Bring your application into focus.
Tell us about your stack. We will help define the right beta setup for your first project.