Skip to content

Manual process: Update input-elastic_agent to v6.2.2 #1212

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.

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
Nov 11, 2021
Merged
Changes from all commits
Commits
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
15 changes: 8 additions & 7 deletions docs/plugins/inputs/elastic_agent.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,9 @@
///////////////////////////////////////////
START - GENERATED VARIABLES, DO NOT EDIT!
///////////////////////////////////////////
:version: v6.2.1
:release_date: 2021-10-11
:changelog_url: https://github.com/logstash-plugins/logstash-input-beats/blob/v6.2.1/CHANGELOG.md
:version: v6.2.2
:release_date: 2021-11-11
:changelog_url: https://github.com/logstash-plugins/logstash-input-beats/blob/v6.2.2/CHANGELOG.md
:include_path: ../../../../logstash/docs/include
///////////////////////////////////////////
END - GENERATED VARIABLES, DO NOT EDIT!
Expand Down Expand Up @@ -233,14 +233,14 @@ Refer to <<plugins-{type}s-{plugin}-ecs_metadata,ECS mapping>> for detailed info
* Default value is 1 executor thread per CPU core

The number of threads to be used to process incoming beats requests.
By default Beats input will create a number of threads equals to 2*CPU cores to handle incoming connections,
reading from the established sockets and execute most of the tasks related to network connection managements,
except the parsing of Lumberjack protocol that's offloaded to a dedicated thread pool.
By default the Beats input creates a number of threads equal to 2*CPU cores.
These threads handle incoming connections, reading from established sockets, and executing most of the tasks related to network connection management.
Parsing the Lumberjack protocol is offloaded to a dedicated thread pool.

Generally you don't need to touch this setting.
In case you are sending very large events and observing "OutOfDirectMemory" exceptions,
you may want to reduce this number to half or 1/4 of the CPU cores.
This will reduce the number of threads decompressing batches of data into direct memory.
This change reduces the number of threads decompressing batches of data into direct memory.
However, this will only be a mitigating tweak, as the proper solution may require resizing your Logstash deployment,
either by increasing number of Logstash nodes or increasing the JVM's Direct Memory.

Expand Down Expand Up @@ -375,3 +375,4 @@ The minimum TLS version allowed for the encrypted connections. The value must be
include::{include_path}/{type}.asciidoc[]

:default_codec!: