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
Copy file name to clipboardExpand all lines: articles/logic-apps/create-standard-workflows-hybrid-deployment.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -224,6 +224,14 @@ For more information, see the following resources:
224
224
225
225
-[Manage revisions in Azure Container Apps](../container-apps/revisions-manage.md)
226
226
227
+
## Set up enhanced telemetry for performance monitoring
228
+
229
+
You can set up enhanced telemetry collection in Application Insights for your Standard logic app resource and then view the collected data after your workflow finishes a run. This capability gives you a simpler experience to get insights about your workflows and more control over filtering events at the data source, which helps you reduce storage costs. These improvements focus on real-time performance metrics that provide insights into your system's health and behavior.
230
+
231
+
With your logic app connected to Application Insights, you can view log data and other metrics in near real time through the Azure portal by using [Live Metrics Stream](/azure/azure-monitor/app/live-stream). You have visualizations to help you plot incoming requests, outgoing requests, and overall health and access to a table of trace level diagnostics. You also have the option to set up your Standard logic app resource to export log and trace data in [OpenTelemetry format](https://opentelemetry.io/). By default, this telemetry data is sent to Application Insights.
232
+
233
+
For more information, see [Enable enhanced telemetry in Application Insights for Standard workflows in Azure Logic Apps](enable-enhanced-telemetry-standard-workflows.md).
234
+
227
235
<aname="change-vcpu-memory"></a>
228
236
229
237
## Change vCPU and memory allocation in the Azure portal
@@ -459,4 +467,5 @@ For more information, see [Container Storage Interface (CSI) drivers on Azure Ku
459
467
460
468
## Related content
461
469
462
-
-[Set up requirements for Standard logic app deployment on your own infrastructure](set-up-standard-workflows-hybrid-deployment-requirements.md)
470
+
-[Set up requirements for Standard logic app deployment on your own infrastructure](set-up-standard-workflows-hybrid-deployment-requirements.md)
471
+
-[Enable enhanced telemetry in Application Insights for Standard workflows in Azure Logic Apps](enable-enhanced-telemetry-standard-workflows.md)
In Application Insights, you can enable enhanced telemetry collection for your Standard logic app resource and then view the collected data after your workflow finishes a run. This capability gives you a simplified experience to discover insights about your workflows and more control over filtering events at the data source, which helps you reduce storage costs. These improvements focus on real-time performance metrics that provide insights into your system's health and behavior. This can help you with proactively detecting and resolving issues earlier.
20
20
21
-
With your logic app connected to Application Insights, you can view log data and other metrics in near real time through the Azure portal by using [Live Metrics Stream](/azure/azure-monitor/app/live-stream).
22
-
You also have visualizations to help you plot incoming requests, outgoing requests, and overall health and access to a table of trace level diagnostics.
21
+
With your logic app connected to Application Insights, you can view log data and other metrics in near real time through the Azure portal by using [Live Metrics Stream](/azure/azure-monitor/app/live-stream). You also have visualizations to help you plot incoming requests, outgoing requests, and overall health and access to a table of trace level diagnostics.
23
22
24
23
The following list describes some example telemetry improvements:
25
24
@@ -29,6 +28,13 @@ The following list describes some example telemetry improvements:
29
28
- More control over filtering non-workflow related events.
30
29
- Advanced filtering that gives you more control over how events are emitted, including triggers and actions.
31
30
31
+
You can also set up your Standard logic app resource to export log and trace data in [OpenTelemetry format](https://opentelemetry.io/). By default, this telemetry data is sent to Application Insights using the Application Insights SDK. However, you can choose to export this data using OpenTelemetry semantics. While you can still use an OpenTelemetry format to send your data to Application Insights, you can also export the same data to any other OpenTelemetry-compliant endpoint. OpenTelemetry provides the following benefits for your logic app:
32
+
33
+
- Correlation across traces and logs generated at the host and in your application code.
34
+
- Consistent, standards-based generation for exportable telemetry data.
35
+
- Integration with other providers that can consume OpenTelemetry-compliant data.
36
+
- Enable OpenTelemetry at the logic app resource level, both in host configuration (host.json) and in your logic app project.
37
+
32
38
This guide shows how to turn on enhanced telemetry collection in Application Insights for your Standard logic app.
33
39
34
40
## Prerequisites
@@ -101,6 +107,48 @@ This guide shows how to turn on enhanced telemetry collection in Application Ins
101
107
102
108
---
103
109
110
+
## Set up OpenTelemetry through Visual Studio Code
111
+
112
+
You can configure your Standard logic app so that the Azure Logic Apps (Standard) runtime emits telemetry in [OpenTelemetry format](https://opentelemetry.io/). However, before you set up OpenTelemetry, consider the following limitations in the current release:
113
+
114
+
- Only the following triggers currently support OpenTelemetry outputs: HTTP, Service Bus, and Event Hubs
115
+
116
+
- Metrics export is currently unsupported.
117
+
118
+
To set up OpenTelemetry capability, follow these steps:
119
+
120
+
1. In your Standard logic app project, open the **host.json** file at the project root level.
121
+
122
+
1. In the **host.json** file, at the root level, add the following **telemetryMode** setting with the **OpenTelemetry** value, for example:
When you enable OpenTelemetry in the **host.json** file, your logic app exports telemetry based on the OpenTelemetry-supported app settings that you define in the environment.
136
+
137
+
1. Open the **local.settings.json** file at the project root level, add the following app settings:
138
+
139
+
| App setting | Description |
140
+
|-------------|-------------|
141
+
|**OTEL_EXPORTER_OTLP_ENDPOINT**| The online transaction processing (OTLP) exporter endpoint URL for where to send the telemetry data. |
142
+
|**OTEL_EXPORTER_OTLP_HEADERS** (optional) | A list of headers to apply to all outgoing data. Commonly used to pass authentication keys or tokens to your observability backend. |
143
+
144
+
1. If your OpenTelemetry endpoint requires other OpenTelemetry-related settings, include these settings in the app settings too.
145
+
146
+
For more information, see the following documentation:
147
+
148
+
-[Edit host and app settings for Standard logic apps](edit-app-settings-host-settings.md)
0 commit comments