Azure
Integration with AppInsights
Severity
P4 - Low (Cosmetic/minor inconvenience)
Describe the Bug with repro steps
Accoring to the documentation
https://learn.microsoft.com/en-us/azure/logic-apps/enable-enhanced-telemetry-standard-workflows?tabs=portal#query-trigger-and-action-events-by-workflow-run-id
when you integrate logic app with AppInsights the Requests.Operation_id column contains the workflowRunId value.
In fact, the default behavior now with the host.json generated by VSCode is different. It appears the OperationId by default now is Incoming OperationId, whatever it may be in different scenarios.
To make the AppInsights integration to behave the default way that @kewear mentioned in his video https://www.youtube.com/watch?v=ZaJM_wFliMM - that is the OperationId = workflowRunId, you now have to manually add
to your host.json the part below:
"extensions":{
"workflow":{
"Settings": {
"Runtime.ApplicationInsightTelemetryVersion": "v2"
}
}
}
If you didn't add the part above manually, the default behavior would as if you specified these two properties:
"extensions":{
"workflow":{
"Settings": {
"Runtime.ApplicationInsightTelemetryVersion": "v2"
"Runtime.ApplicationInsights.PreserveIncomingOperationId": "true"
}
}
}
Please add the required entries to the VSCode generated host.json or/and update the documentation. It may save people many hours of googling with pretty much no useful information, until you come across the video and start experimenting with the settings.
What type of Logic App Is this happening in?
Standard (VSCode)
Are you experiencing a regression?
No response
Which operating system are you using?
Windows
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Screenshots or Videos
No response
Environment
Chrome Ext 5.165.5
Additional context
No response
When no logging settings are specified in host.json, the behavior you are mentioning is expected as the Runtime.ApplicationInsightTelemetryVersion is default "v1". In "v1" telemetry the OperationId by default is Incoming OperationId by default.
We have plans to make "v2" telemetry as default behavior in upcoming releases.
Thanks, @nikhilsira for the reply.
How do I make it then with V1 to use workflowRunId instead of Incoming OperationId?
Unless I misinterpreted it, @kewear in his video (link in the original post) said the default behavilor of the V1 was RunId and that one of the purposes of the V2 was to give an option to use the IncomingOperationId instead of RunId. The product documentation (link in the original post) also implies that operation_id = RunId.
