You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[BUG] Http triggered Azure Function throws System.UriFormatException, no support for Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore integration?
#2311
Operating system and version:
At least Windows, but I guess this isn't OS spesific.. .NET Framework/Core name and version
Dotnet 8, Azure Functions
Describe the bug
Using the APM package for a HTTP Triggered Azure Function fails when the Azure Function uses the 'Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore' integration. This integration seems to be the default when creating a HTTP Triggerend function app in Visual Studio as well.
When triggering the function, the APM Middleware throws an System.UriFormatException . The exception is thrown in the method Elastic.Apm.Azure.Functions.ApmMiddleware.GetTriggerSpecificData.
To Reproduce
Steps to reproduce the behavior:
Create HTTP Triggered function app and add the middelware ApmMiddelware
Trigger the Function
Watch it failing...
Expected behavior
The APM integration for Azure Functions should support the default behaviour implemented by Microsofts own templates.
The text was updated successfully, but these errors were encountered:
APM Agent version
Elastic.Apm.Azure.Functions version 1.26.0
Environment
Operating system and version:
At least Windows, but I guess this isn't OS spesific..
.NET Framework/Core name and version
Dotnet 8, Azure Functions
Describe the bug
Using the APM package for a HTTP Triggered Azure Function fails when the Azure Function uses the 'Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore' integration. This integration seems to be the default when creating a HTTP Triggerend function app in Visual Studio as well.
When triggering the function, the APM Middleware throws an
System.UriFormatException
. The exception is thrown in the methodElastic.Apm.Azure.Functions.ApmMiddleware.GetTriggerSpecificData
.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The APM integration for Azure Functions should support the default behaviour implemented by Microsofts own templates.
The text was updated successfully, but these errors were encountered: