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
My team recently started using Microsoft.Azure.Functions.Worker.ApplicationInsights NuGet version 1.0.0-preview4 (we were using Microsoft.ApplicationInsights.WorkerService version 2.21.0) and we noticed that the Application Insights logs don't have operation_Name dimension but they have a AzureFunctions_FunctionName custom dimension.
Is the intention to replace operation_Name with AzureFunctions_FunctionName? If it isn't, is there a way to have operation_Name back in the logs?
The text was updated successfully, but these errors were encountered:
We are starting to work to align our telemetry better with industry standards, which would include operation_Name being set for you when using App Insights. The proposal is here: Azure/azure-functions-host#9273
However, you can add your own ITelemetryProcessor or ITelemetryInitializer to set it for now - you can read AzureFunctions_FunctionName and set operation_Name. Or set it to whatever works best for you.
My team recently started using Microsoft.Azure.Functions.Worker.ApplicationInsights NuGet version 1.0.0-preview4 (we were using Microsoft.ApplicationInsights.WorkerService version 2.21.0) and we noticed that the Application Insights logs don't have
operation_Name
dimension but they have aAzureFunctions_FunctionName
custom dimension.Is the intention to replace
operation_Name
withAzureFunctions_FunctionName
? If it isn't, is there a way to haveoperation_Name
back in the logs?The text was updated successfully, but these errors were encountered: