Skip to content

update hosts onboarding flow configuration issue #3654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 26, 2025
Merged

update hosts onboarding flow configuration issue #3654

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9a7cf27
update hosts onboarding flow configuration issue
vigneshshanmugam Oct 25, 2025
fcd224a
Update known-issues.md
theletterf Oct 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions release-notes/elastic-observability/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -156,5 +156,38 @@ After upgrading a cluster, Collector and Symbolizer endpoints may not be configu
DELETE kbn:/api/fleet/package_policies/<elastic-universal-profiling-symbolizer-id>?force=true
```

::::

:::{dropdown} Error when using the Opentelemetry onboarding flow using EDOT Collector
Applies to: {{stack}} 9.1.6, 9.2.0

**Details**

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:

```
> sudo ./otelcol --config otel.yml

Starting in otel mode
failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):

'exporters' error reading configuration for "otlp/ingest": decoding failed due to the following error(s):

'sending_queue' decoding failed due to the following error(s):

'batch' decoding failed due to the following error(s):

'' has invalid keys: flush_interval

```

**Workaround**

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`.

```yaml
batch:
flush_timeout: 1s
```

::::