Skip to content

Commit 24ca5e3

Browse files
update hosts onboarding flow configuration issue (elastic#3654)
+ Adds the otel mode configuration issue to the known issue list with the workaround - #10822 --------- Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
1 parent 9b6507e commit 24ca5e3

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed

release-notes/elastic-observability/known-issues.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -156,5 +156,38 @@ After upgrading a cluster, Collector and Symbolizer endpoints may not be configu
156156
DELETE kbn:/api/fleet/package_policies/<elastic-universal-profiling-symbolizer-id>?force=true
157157
```
158158
159+
::::
160+
161+
:::{dropdown} Error when using the Opentelemetry onboarding flow using EDOT Collector
162+
Applies to: {{stack}} 9.1.6, 9.2.0
163+
164+
**Details**
165+
166+
Users trying to collect logs and host metrics using the Elastic distribution of the OTel collector will see error when using the OpenTelemetry quickstart onboarding flow:
167+
168+
```
169+
> sudo ./otelcol --config otel.yml
170+
171+
Starting in otel mode
172+
failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):
173+
174+
'exporters' error reading configuration for "otlp/ingest": decoding failed due to the following error(s):
175+
176+
'sending_queue' decoding failed due to the following error(s):
177+
178+
'batch' decoding failed due to the following error(s):
179+
180+
'' has invalid keys: flush_interval
181+
182+
```
183+
184+
**Workaround**
185+
186+
To work around this issue, manually update the configuration of the generated `otel.yaml` file to replace incorrect key `flush_interval` with the correct key `flush_timeout`.
187+
188+
```yaml
189+
batch:
190+
flush_timeout: 1s
191+
```
159192
160193
::::

0 commit comments

Comments
 (0)