-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET CaptureBlockingCalls external code #3940
Comments
Hi @btecu , The only way to selectively capture blocking calls at the moment is by suppressing it for certain code blocks: sentry-dotnet/samples/Sentry.Samples.AspNetCore.Mvc/Controllers/HomeController.cs Lines 45 to 48 in d1e5efc
Does that help in your situation? |
It doesn't, that's not really feasible, is it? Can't edit external packages code which is already compiled anyway to add |
It depends whether you're calling the code in the external package explicitly or not. So my question was whether you're seeing blocking calls in external code that is ultimately invoked indirectly by your code or whether that code just "magically" gets run by the framework (which is probably the case for lots of middleware in ASP.NET Core). |
If it was caused by internal code, there would be a line at the beginning of the stack trace where it references the call to say |
It looks like
CaptureBlockingCalls = true
also reports on external code (ASP .NET Core, nuget packages), which is really not actionable:Is there a way to only capture local code?
Using .NET 9.
The text was updated successfully, but these errors were encountered: