[EDR Workflows][Process descendants filter] Display process descendant filtering on event filter cards

[gergoabraham]

Summary

The modifications indicate to the users if an Event Filter filters process descendants, displayed on Event Filters page and on Policy page's Event Filters tab (todo).

Checklist

Delete any items that are not applicable to this PR.

• [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• [ ] Documentation was added for features that require explanation or tutorials
• [ ] Unit or functional tests were updated or added to match the most common scenarios
• [ ] Flaky Test Runner was used on any tests changed
• [ ] Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• [ ] This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• [ ] This was checked for cross-browser compatibility

[gergoabraham]

@ferullo @caitlinbetz at the moment indicating Process Descendant filtering looks like below. can we live with this? :)

[ferullo]

@ferullo @caitlinbetz at the moment indicating Process Descendant filtering looks like below. can we live with this? :)

Yes. It looks great. 💯

[elasticmachine]

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

[gergoabraham]

@elasticmachine merge upstream

[gergoabraham]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: d556750
• Interpreting CI Failures

Failed CI Steps

• FTR Configs #46
• Check Types

Test Failures

• [job] [logs] FTR Configs #46 / @skipInServerless endpoint @ess @serverless For each artifact list under management When on the Event Filters entries list should be able to add a new Event Filters entry

History

To update your PR or re-run it, just comment with: @elasticmachine merge upstream

cc @gergoabraham

note: the failing test looked suspicious, because it's related to event filters, and even worse, the first occurrence was during kibana-on-merge for the previous process descendant PR:

• test fail issue: https://github.com/elastic/kibana/issues/187314
• previous PR that triggered it on-merge: https://github.com/elastic/kibana/pull/187141

but fortunately, it looks like coincidence 😌 locally the test has passed, and the similar errors happened previously:

• https://github.com/elastic/kibana/issues/186004
• https://github.com/elastic/kibana/issues/186004

[kibana-ci]

:yellow_heart: Build succeeded, but was flaky

• Buildkite Build
• Commit: 5b7cf8831db6e87bc8317d87e44999243c8a0c3e

Failed CI Steps

• Jest Tests #10
• Defend Workflows Cypress Tests on Serverless #1

Test Failures

• [job] [logs] Jest Tests #10 / ColumnsPopover renders correctly a list of selected columns

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	5583	5585	+2

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
securitySolution	15.5MB	15.6MB	+5.3KB

History

• :yellow_heart: Build #219021 was flaky bab59f1a78924b9efe080e91bf9947b77da1ec1f
• :broken_heart: Build #218994 failed d556750cb9922e9d20897bd9de51b68cd8749b16

To update your PR or re-run it, just comment with: @elasticmachine merge upstream

cc @gergoabraham