For ASP.NET Core
ErrorDock for ASP.NET Core.
ErrorDock integrates with ASP.NET Core through middleware registered in the request pipeline, and unhandled exceptions are captured with full request context. Endpoint timing comes from OpenTelemetry: with the ASP.NET Core and Entity Framework Core instrumentation forwarded to ErrorDock through an OpenTelemetry Collector, every endpoint gets P50 through P99 latency and its queries appear in the trace.
Two lines in Program.cs
Add the service registration and the middleware. Exception capture and release tagging start immediately, with no attributes to sprinkle through controllers and no wrapper types to inherit from. The ErrorDock packages emit no spans; request timing is OpenTelemetry's job, configured alongside.
Request context on every exception
Route, method, status code, headers you have allow-listed, the authenticated user identifier you configure and the correlation id all travel with the exception, so an issue arrives with the context you would otherwise have gone looking for in logs.
Endpoint performance and N+1 queries
With the OpenTelemetry spans arriving, every endpoint gets P50 to P99 latency and an error rate. Slow requests expand into a span waterfall where a repeated EF Core query renders as a repeated span, which is what makes an N+1 obvious rather than merely present.
Frequently asked questions
- Where in the pipeline should the middleware go?
- After UseExceptionHandler and before the endpoints, so an exception reaches it before the exception handler converts it into a response. The docs show the exact ordering.
- Does it interfere with my existing exception handling?
- No. ErrorDock observes and re-throws; it does not swallow exceptions or change the response your own handler produces.
Related
- ErrorDock for .NET. ErrorDock for .NET: exception monitoring with portable PDB stack traces, product analytics and locally evaluated feature flags, with a NuGet package for each kind of host and performance from OpenTelemetry.
- 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.
- .NET error monitoring. How exception handling, logging and error monitoring fit together in .NET, and what to capture from an ASP.NET Core application.
Bring your application into focus.
Tell us about your stack. We will help define the right beta setup for your first project.