Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Spans are not automatically captured for HTTP calls completed with exception on .NET Full Framework
See original GitHub issueFor example, when testing /Home/FailingOutGoingHttpCall of sample\AspNetFullFrameworkSampleApp (the issue is reproducible both when the application running on top of IIS and IIS Express).
It seems that in that case IDiagnosticListener on .NET Framework doesn’t receive HTTP-request-failed event as it does happen on .NET Core.
In /Home/FailingOutGoingHttpCall HTTP call fails because host name is nonexistent, i.e., DNS resolution failure - we also need to cover cases when HTTP call fails because it’s timed out and/or server forcibly closed connection. elastic/apm-agent-dotnet#293 is the issue to implement the same kind of tests for .NET Core.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@SergeyKleyman I’m sorry for the delay (you must get that a lot). I have since removed the use of the IDiagnosticListener and created my own handlers for HttpClient and API pipeline. These are working well
Bigger problem: we only receive the start event and we create a span for that and store the request - problem is we don’t get any event for the exception or end. Probably as the 1. step we should make sure we don’t cause too much memory usage due to this.