@@ -165,7 +165,6 @@ Before you deploy this template, replace placeholders surrounded by `<>` with yo
165
165
}
166
166
```
167
167
168
-
169
168
# [ Azure CLI] ( #tab/azure-cli )
170
169
171
170
Before you run this command, replace placeholders surrounded by ` <> ` with your values.
@@ -178,6 +177,11 @@ az containerapp env telemetry data-dog set \
178
177
--enable-open-telemetry-metrics true
179
178
```
180
179
180
+ # [ Terraform] ( #tab/terraform )
181
+
182
+ ``` hcl
183
+ ```
184
+
181
185
---
182
186
183
187
## OTLP endpoint
@@ -246,6 +250,11 @@ az containerapp env telemetry otlp add \
246
250
--enable-open-telemetry-logs true
247
251
```
248
252
253
+ # [ Terraform] ( #tab/terraform )
254
+
255
+ ``` hcl
256
+ ```
257
+
249
258
---
250
259
251
260
| Name | Description |
@@ -274,9 +283,8 @@ To configure an agent, use the `destinations` array to define which agents your
274
283
- You can only set up one Application Insights and Datadog endpoint each at a time.
275
284
- While you can define more than one OTLP-configured endpoint, each one must have a distinct name.
276
285
277
-
278
- The following example shows how to use an OTLP endpoint named ` customDashboard ` . It sends:
279
- - traces to app insights and ` customDashboard `
286
+ The following example ARM template shows how to use an OTLP endpoint named ` customDashboard ` . It sends:
287
+ - traces to app insights and ` customDashboard `
280
288
- logs to app insights and ` customDashboard `
281
289
- metrics to DataDog and ` customDashboard `
282
290
@@ -308,6 +316,7 @@ The following example shows how to use an OTLP endpoint named `customDashboard`.
308
316
}
309
317
}
310
318
}
319
+ ```
311
320
312
321
## Example OpenTelemetry configuration
313
322
0 commit comments