Skip to content
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

Documentation for byte-based ingestion limits in Agent #1061

Open
kilfoyle opened this issue May 6, 2024 · 0 comments
Open

Documentation for byte-based ingestion limits in Agent #1061

kilfoyle opened this issue May 6, 2024 · 0 comments
Assignees

Comments

@kilfoyle
Copy link
Contributor

kilfoyle commented May 6, 2024

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):

    • If any byte-based parameters are explicitly configured, all event-based defaults are ignored.
    • If any event-based limits are explicitly configured, all byte-based defaults are ignored.
    • If neither parameter type is explicitly configured, fall back on the global default (currently event-based).

It seems all settings will apply to Elasticsearch only, for now, with Logstash TBD.

Related Beats issue: https://github.com/elastic/beats/issues/30069

@kilfoyle kilfoyle self-assigned this May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant