Upgrading telemetry for better monitoring, faster troubleshooting, and reliable integration at scale
This post is part of our Logic Apps Observability series. See Part 2 on applying the Logic App Overview Workbook Template, and Part 3 on customizing the workbook for multi-workflow monitoring.
If you’ve ever tried diagnosing a Logic App Standard workflow using the old telemetry, you know the frustration. Generic traces, missing context, and too much time wasted digging. Application Insights v2 telemetry changes that. With one small configuration update, you gain richer diagnostics, smarter filters, and true cross-service correlation. This is not just an upgrade in logging. It is a leap forward in operational efficiency and reliability.
Enhanced (v2) telemetry delivers significant benefits:
Action Level Clarity: Trigger and action events capture connector type and API name.
Retry and Exception Tracking: Failures and retries are logged with useful context.
Reduced Noise: Streamlined logging reduces data sprawl and storage costs.
Cross Service Correlation: Preserve operation IDs across Logic Apps, API Management, and Functions for true end to end tracing.
OpenTelemetry Support: Export to Application Insights or any OTEL-compliant endpoint for standardized observability.
For BizTalk veterans, this feels like the modern answer to Group Hub reporting. Robust, actionable, and cloud native.
Update your Logic App Standard host.json file with this snippet:
{
"version": "2.0",
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows",
"version": "[1, 2.00)"
},
"extensions": {
"workflow": {
"Settings": {
"Runtime.ApplicationInsightTelemetryVersion": "v2"
}
}
}
}Open your Logic App Standard resource in Azure Portal.
Navigate to Development Tools → Advanced Tools (Kudu).
This will open the Kudo tools page. Select “Debug Console → CMD”
This will open the site folder directory. From here you can navigate to the host.json file by following: site → wwwroot → host.json.
Edit and update the file with the JSON snippet above. Select the “pencil” edit icon to update the file. If it does not include the Runtime.ApplicationInsightTelemetryVersion node, replace the JSON in the host.json file and click Save.
After saving the changes to the host.json file, the tab can be closed, and the changes should be automatic. You can also restart the Logic App from the Overview tab of the Logic App Standard resource.
For multi-service correlation, add the PreserveIncomingOperationId node:
"Runtime.ApplicationInsights.PreserveIncomingOperationId": "true"This setting ensures that operation IDs are preserved when Logic Apps call or trigger other services, which enables true end to end correlation across multiple workflows and platforms
{
"version": "2.0",
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows",
"version": "[1, 2.00)"
},
"extensions": {
"workflow": {
"Settings": {
"Runtime.ApplicationInsightTelemetryVersion": "v2",
"Runtime.ApplicationInsights.PreserveIncomingOperationId": "true"
}
}
}
}Faster Issue Resolution: Filter failed runs and pinpoint root causes in seconds.
Improved Observability: Trace workflows across Logic Apps, APIs, and Functions.
Operational Efficiency: Lower storage costs, cleaner logs, and more actionable data.
Happier Teams: Operations staff finally get dashboards that show clarity instead of clutter.
This article is part of our Logic Apps Observability series. Explore Part 2 on applying the Logic App Overview Workbook Template, and Part 3 on customizing the workbook for multi-workflow monitoring.
If troubleshooting is slowing down your operations team, it is time to modernize. Phidiax architects can help you enable v2 telemetry, implement observability driven workbooks, and ensure monitoring aligns directly with your business outcomes.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。