LOG-3883: Implement pruning fields from log messages

[Clee2691]

Description

This PR adds the prune filter feature. This feature allows admins to prune fields from log records to reduce the overall size of a record.

This feature extends the filter API by adding the fields prune along with in and notIn.

The fields, in and notIn, expect an array of dot-delimited path expressions which should contain alphanumeric and underscores. Anything outside of that will have to be quoted.

• Ex1 : .kubernetes."foo-bar/baz"
• Ex2: .log_type

An example prune filter spec is as follows:

spec:
  filters:
    - name: my-prune
      type: prune
      prune:
        in: [.kubernetes.namespace_name,.foo."test-dashes/slashes"]
        notIn: [.log_type,.message,.kubernetes,."@timestamp",.openshift]

/cc @cahartma @vparfonov
/assign @jcantrill

Links

• JIRA: https://issues.redhat.com/browse/LOG-3883
• Enhancement proposal: https://github.com/openshift/enhancements/blob/a6a1feb9cceb0b61960bcf00f292cb0d04ee3753/enhancements/cluster-logging/content-filter.md#prune-filters

[openshift-ci-robot]

@Clee2691: This pull request references LOG-3883 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.8.0" version, but no target version was set.

In response to this:

Description

This PR adds the prune filter feature. This feature allows admins to prune fields from log records to reduce the overall size of a record.

This feature extends the filter API by adding the fields prune along with in and notIn.

The fields, in and notIn, expect an array of dot-delimited path expressions which should contain alphanumeric and underscores. Anything outside of that will have to be quoted.

• Ex1 : .kubernetes."foo-bar/baz"
• Ex2: .log_type

An example prune filter spec is as follows:

spec:
 filters:
   - name: my-prune
     type: prune
     prune:
       in: [.kubernetes.namespace_name,.foo."test-dashes/slashes"]
       notIn: [.log_type,.message,.kubernetes,."@timestamp",.openshift]

/cc @cahartma @vparfonov
/assign @jcantrill

Links

• JIRA: https://issues.redhat.com/browse/LOG-3883
• Enhancement proposal: https://github.com/openshift/enhancements/blob/a6a1feb9cceb0b61960bcf00f292cb0d04ee3753/enhancements/cluster-logging/content-filter.md#prune-filters

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[Clee2691]

/hold

[Clee2691]

/retest

[jcantrill]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Clee2691, jcantrill

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:

• OWNERS [jcantrill]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Clee2691]

/hold cancel

[vparfonov]

can we use exist function instead of get https://vector.dev/docs/reference/vrl/functions/#exists ?

[Clee2691]

I am using get here because I broke up the field path into an array of path segments. The get function expects an array instead of a path. I could not use something like:

paths = [.log, .message]

and iterate through that because for_each would only extract the values and not preserve the path for the exists function.

[Clee2691]

/hold cancel

[Clee2691]

/retest

[vparfonov]

/lgtm

[openshift-ci]

@Clee2691: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.