Skip to content

[Feature]: Per-beat extra_config passthrough for unmanaged settings #512

Description

@afeefghannam89

The Beats templates are opinionated, so any setting without a dedicated role variable (e.g. queue.*, max_procs, http, custom processors) can't be set.

Add a beats_filebeat_extra_config / beats_metricbeat_extra_config / beats_auditbeat_extra_config dict (default {}), appended to the generated config via to_nice_yaml. Only for top-level keys the role does not already manage (setting a managed key like output.* would duplicate it). Not argument_specs-validated — the escape hatch for the long tail. Non-breaking (empty default).

Complements #505/#510 (which only cover the inputs/modules sections), this targets the top-level keys the role doesn't manage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    component:beatsroles/beats - shared, or several beats at oncefeatureNew capability or new variable for users

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions