elastic / elastic/elastic-agent

Proper support for global processor overrides

Open
#13,148 2 comments 0 reactions 0 assignees View on GitHub
Agent bug Team:Elastic-Agent Team:Elastic-Agent-Control-Plane
Dominant language
Go
Stars
275
Forks
264
Avg merge
1d 23h
Merged PRs (30d)
312

Description

at this time we can specify global processors in controller by using elastic-agent config (fleet.yml) with fleet_override enabled.

If we specify global processor fleet.yml contains
```yml
processors:
- list

outputs.processors: [proc1]
```

issue is these values will overwrite any other processors or output processors defined by user in fleet.
Idea is to append global ones defined in fleet yml just after policy defined collection

Contributor guide

Open the contributing guide

Research direction

Start with the fleet_override handling for processors in fleet.yml and trace how policy-defined collections are combined with global processors. Verify the current behavior for processors and outputs.processors, then define completion as appending the global entries after policy-defined ones without overwriting user values.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.