Skip to content

Add known issue that Beats do not recover from transient network errors #1312

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 1 commit into from
Sep 11, 2024
Merged

Add known issue that Beats do not recover from transient network errors #1312

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
19 changes: 19 additions & 0 deletions docs/en/ingest-management/release-notes/release-notes-8.15.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,25 @@ Review important information about the {fleet} and {agent} 8.15.1 release.
[[known-issues-8.15.1]]
=== Known issues

[[known-issue-issue-40705]]
.{beats} based integrations stop publishing data after a network error unless restarted.
[%collapsible]
====

*Details*

A bugfix merged for 8.15.1 can cause repeated `Get \"https://${ELASTICSEARCH_HOST}:443\": context canceled` errors
after a transient network error (for example DNS failure) that prevent {agent} integrations based on {beats} from publishing data.
{agent} must be restarted for publishing to continue.

See {beats} issue link:https://github.com/elastic/beats/issues/40705[#40705] for details.

*Impact* +

Avoid upgrading to 8.15.1.

====

[[known-issue-issue-191730]]
.Fleet configures additional properties in some nested objects in index templates of integrations.
[%collapsible]
Expand Down