-
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
[BUG] Dotnet Azure Function Not captured in elastic #2407
Comments
Thanks for bringing this to our attention @Elsakrishi29 do you get any azure logs from the invocation? |
Every time I add Elastic configuration to my application, it fails to work properly. If i removed those configuration in my application it will work fine logs
Configuration |
Seems to be a duplicate of #2311 .ConfigureFunctionsWorkerDefaults(builder =>
{
builder.UseMiddleware<ApmMiddleware>();
})
.ConfigureFunctionsWebApplication() -> calls "ConfigureFunctionsWorkerDefaults" internally too Does it work without the |
stevejgordon
added a commit
that referenced
this issue
Nov 29, 2024
This PR fixes several things in Azure Functions (isolated worker) which occur when using the latest templates for Azure Functions. - Newer versions of the Functions library prefer the gRPC-based implementation, which throws when `Url` is accessed. Instead, we read these from other data on the `FunctionContext`. - Address Functions library changes that break distributed tracing. We now parse the original headers from the `BindingContext` instead of the request, which may contain a `traceparent` with the sampling flag set to false when the user request does not include a specific `traceparent`. - We explicitly don't record activities from the Azure functions library as these are pretty broken (Azure/azure-functions-dotnet-worker#2733) and are redundant when using our middleware. - Downgrade several packages as the newer ones are now deprecated (thanks for the confusion, Microsoft!). - Update some outdated compiler pre-processor directives. - The final few commits focus on CI integration test hangs on Linux. We don't have a perfect solution for those, but after reviewing the hang dumps, I've avoided some of the potential causes of the hangs. We'll monitor subsequent PRs, and if they remain stable, we will readdress the original causes. A follow-up PR will update our documentation. Closes #2407 Closes #2311 Closes #2218
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We followed this link to add elastic dotnet apm agent to our azure function.
The functions are not captured in elastic, then I didn't get any logs in my azure cloud function. ( After integrating the Elastic APM tracing middleware into my Azure Functions app, the function executes successfully but does not return any data or response when accessing the endpoint. The function works correctly when the middleware is not included )
Agent instrumentation (Program.cs)
Could someone please help me figure out why this error is occurring?
The text was updated successfully, but these errors were encountered: