-
Notifications
You must be signed in to change notification settings - Fork 927
new(userspace): static fields #3557
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
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: FedeDP The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/milestone 0.42.0 |
CI build-dev is failing because it uses yaml-cpp from the system that is too old and does not support EDIT: fixed by porting the code to use a |
Example rule output with: static_fields:
foo: bar
foo2: ${HOME} 👇
|
Relevant PRs have been merged in libs master; once #3592 is merged i will rebase this one and get it ready. |
…ema. Signed-off-by: Federico Di Pierro <[email protected]>
Signed-off-by: Federico Di Pierro <[email protected]>
What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
The PR adds a new
static_fields
configuration object; each{key,value}
pair will be used as static field that will be automatically appended to the output (ifappend_output.suggested_output
is enabled), and can be used as rule condition.Which issue(s) this PR fixes:
Fixes #3554
Special notes for your reviewer:
This PR depends upon falcosecurity/libs#2405, keeping this
wip
until that PR is merged.Does this PR introduce a user-facing change?: