We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Agent (and Beats) output will be limitable by bytes, as an addition to current events-based limits.
Proposal document
We'd need to document:
The new output settings:
bulk_max_bytes
queue.mem.bytes
queue.disk.input_memory_byte_limit
queue.disk.output_memory_byte_limit
Resolution between conflicting settings (see "Interaction with existing defaults" section):
It seems all settings will apply to Elasticsearch only, for now, with Logstash TBD.
Related Beats issue: https://github.com/elastic/beats/issues/30069
https://github.com/elastic/beats/issues/30069
The text was updated successfully, but these errors were encountered:
kilfoyle
No branches or pull requests
Agent (and Beats) output will be limitable by bytes, as an addition to current events-based limits.
Proposal document
We'd need to document:
The new output settings:
bulk_max_bytes
queue.mem.bytes
queue.disk.input_memory_byte_limit
queue.disk.output_memory_byte_limit
Resolution between conflicting settings (see "Interaction with existing defaults" section):
It seems all settings will apply to Elasticsearch only, for now, with Logstash TBD.
Related Beats issue:
https://github.com/elastic/beats/issues/30069
The text was updated successfully, but these errors were encountered: