-
Notifications
You must be signed in to change notification settings - Fork 206
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
Fixes and enhancements for Azure Functions (isolated worker) #2505
Conversation
Due to implementation changes in the Functions libraries we have to attempt a different method to collect the HTTP information we need. This also wraps the code in a try/catch to avoid potential exceptions from breaking the entire Function invocation.
When developing locally, various headers we expect to use to get meta data for the service are not available. We should still set what we can so that in local development the APM server does not return a 400 error.
@stevejgordon Thank you for handling this. we were experiencing the issue #2311 in my organization (we figured it out the same day you have decided to tackle it ... strange coincidence) |
You're welcome, @alaeddineG. I'm afraid there's no preview channel. I can't commit fully, but I aim to release it next week. |
@alaeddineG 1.31.0 was released today and includes the fixes that I hope address the issues above. |
@stevejgordon Thank you a lot, my team have switched to the new version and they told me the Issue #2311 is fixed ! |
This PR fixes several things in Azure Functions (isolated worker) which occur when using the latest templates for Azure Functions.
Url
is accessed. Instead, we read these from other data on theFunctionContext
.BindingContext
instead of the request, which may contain atraceparent
with the sampling flag set to false when the user request does not include a specifictraceparent
.A follow-up PR will update our documentation.
Closes #2407
Closes #2311
Closes #2218