Skip to content

Commit dd71103

Browse files
committed
AIO observability: update YAML
1 parent f7893bc commit dd71103

1 file changed

Lines changed: 19 additions & 25 deletions

File tree

articles/iot-operations/configure-observability-monitoring/howto-configure-observability.md

Lines changed: 19 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to deploy Azure IoT Operations observability resources, c
44
author: sethmanheim
55
ms.author: sethm
66
ms.topic: how-to
7-
ms.date: 11/20/2025
7+
ms.date: 12/19/2025
88

99
# CustomerIntent: As an IT admin or operator, I want to be able to monitor and visualize data on the health of my industrial assets and edge environment.
1010
---
@@ -98,61 +98,55 @@ Define and deploy an [OpenTelemetry (OTel) Collector](https://opentelemetry.io/d
9898
image:
9999
repository: otel/opentelemetry-collector
100100
tag: 0.107.0
101+
101102
config:
102103
processors:
103104
memory_limiter:
104105
limit_percentage: 80
105106
spike_limit_percentage: 10
106-
check_interval: '60s'
107+
check_interval: 60s
108+
107109
receivers:
108-
jaeger: null
109-
prometheus: null
110-
zipkin: null
111110
otlp:
112111
protocols:
113112
grpc:
114-
endpoint: ':4317'
113+
endpoint: ":4317"
115114
http:
116-
endpoint: ':4318'
115+
endpoint: ":4318"
116+
117117
exporters:
118118
prometheus:
119-
endpoint: ':8889'
119+
endpoint: ":8889"
120120
resource_to_telemetry_conversion:
121121
enabled: true
122122
add_metric_suffixes: false
123+
123124
service:
124125
extensions:
125126
- health_check
127+
128+
telemetry:
129+
metrics:
130+
readers: []
131+
126132
pipelines:
127133
metrics:
128134
receivers:
129135
- otlp
130136
exporters:
131137
- prometheus
132-
logs: null
133-
traces: null
134-
telemetry: null
135-
extensions:
136-
memory_ballast:
137-
size_mib: 0
138+
138139
resources:
139140
limits:
140-
cpu: '100m'
141-
memory: '512Mi'
141+
cpu: "100m"
142+
memory: "512Mi"
143+
142144
ports:
143145
metrics:
144146
enabled: true
145147
containerPort: 8889
146148
servicePort: 8889
147-
protocol: 'TCP'
148-
jaeger-compact:
149-
enabled: false
150-
jaeger-grpc:
151-
enabled: false
152-
jaeger-thrift:
153-
enabled: false
154-
zipkin:
155-
enabled: false
149+
protocol: TCP
156150
```
157151
158152
1. In the `otel-collector-values.yaml` file, make a note of the following values that you use in the `az iot ops create` command when you deploy Azure IoT Operations on the cluster:

0 commit comments

Comments
 (0)