Skip to content
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

Tracee-eBPF Filter configuration API #1726

Closed
2 tasks done
NDStrahilevitz opened this issue May 3, 2022 · 1 comment
Closed
2 tasks done

Tracee-eBPF Filter configuration API #1726

NDStrahilevitz opened this issue May 3, 2022 · 1 comment
Assignees

Comments

@NDStrahilevitz
Copy link
Collaborator

NDStrahilevitz commented May 3, 2022

Prerequisites

  • This issue is an EPIC issue (add label: EPIC).

Select one OR another:

  • I'll create a PR to implement this feature (assign to yourself).

Feature description

The API should allow configuration of filters, with parity to the filter capabilities of the CLI. It should be integrated into the API interface that tracee-ebpf exposes as described in #1725

The API should allow adding new filters, updating existing filters and deleting filters. Filters should be reconciled after a request, and a response should indicate any filter changes due to reconciliation.

#1727: In order to enable the logic for filter conflict resolving, an internal Filter API should be implemented.
#1830: To enable sending per event context filters.

Additional Information (feature drawings, files, logs, etc)

image

@yanivagman yanivagman changed the title [EPIC] Tracee-eBPF Filter configuration API Tracee-eBPF Filter configuration API Jan 31, 2023
@yanivagman yanivagman mentioned this issue Feb 7, 2023
5 tasks
@yanivagman yanivagman mentioned this issue Apr 9, 2023
4 tasks
@yanivagman
Copy link
Collaborator

Closing in favor of #2991

@yanivagman yanivagman closed this as not planned Won't fix, can't repro, duplicate, stale Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants