Cherry-pick #26275 to 7.13: Enable agent to send custom headers to kibana/ES #26362
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #26275 to 7.13 branch. Original message:
What does this PR do?
This PR modifies
container
andenroll
commands to accept list of headers which are then sent to kibana/ES when fleet-server or metric/file beat send events or performs setup.Headers are hold in memory and are added to ES output in opt-in manner using
inject_custom_headers
rules in a spec file.Why is it important?
To stay in par with other products working in cloud
Fixes: ##26137
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.