-
Notifications
You must be signed in to change notification settings - Fork 382
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
Allow event filtering based on tracing policy #1867
Conversation
✅ Deploy Preview for tetragon ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
8ad79e5
to
b14a096
Compare
Thanks! started the tests, and added a release note! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey!! Thanks a lot for those patches, I think they all make sense and I would like to merge them!
This is a bit of a nit but the commits are not really related, would it be possible to split this PR into two PRs? Maybe this one for the filtering based on the tracing policy name, and another one for the docs? If this is too annoying tell me and we'll figure something else.
Also if you can rebase since we fixed something in the CI in the meantime. Sorry for the delay, it was the Christmas period! 🎄
I'm also good with merging this once @mtardy's comments have been addressed. |
+1 appears useful please address feedback and we can get this merged! :) |
That's good to hear, thanks!
Sure, I can split changes into 2 PRs.
Definitely, will do. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Everything looks good to me.
I'd prefer if the last patch was split into multiple patches, such as
- documentation fixes (typos)
- core code changes
- tetra CLI
But I don't think we should block the PR on this.
Could you please address the comments from everyone and have the documentation change also work in bash?
Other than that, good to go from my side!
b14a096
to
6d05c15
Compare
Update:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Many thanks! LGTM
I did not have the time to re-test functionality, I can do that in the following days (if needed)
Is there testing that is not covered by the unit tests?
As far as I can see, there were no changes in the code (other than the rebasing) and you have unit tests so, at least from my side, it's good to merge.
Indeed, just mentioned this for completeness. I'm good to proceed. |
@mtardy now that your comments have been addressed maybe approve this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot, and thanks for adding tests, let's merge that :)
I can't merge because of this @willfindlay, could you review it? Lines 4 to 5 in 0a9b71e
In the meantime @ioandr if you can ever rebase this on main (I'm sorry I wanted to merge this now), I fixed the CI issue that made vmtests fail early. |
Signed-off-by: Ioannis Androulidakis <[email protected]>
Extend the list of filters with a new one to support filtering events based on the name of a tracing policy. Closes cilium#1855 Signed-off-by: Ioannis Androulidakis <[email protected]>
Closes cilium#1855 Signed-off-by: Ioannis Androulidakis <[email protected]>
6d05c15
to
fee4776
Compare
Thanks for the rebase, everything is green, now just waiting on William's ack. |
Merged, thanks |
In cilium#1867, the `--policy-names` flag was added to filter events based on the tracing policy. However, the filter was only appled to `kprobe` events. This patch extends the filter to support all events types: `tracepoint`, `uprobe` and `lsm`. Signed-off-by: Justin Chen <[email protected]>
In cilium#1867, the `--policy-names` flag was added to filter events based on the tracing policy. However, the filter was only appled to `kprobe` events. This patch extends the filter to support all events types: `tracepoint`, `uprobe` and `lsm`. Signed-off-by: Justin Chen <[email protected]>
In cilium#1867, the `--policy-names` flag was added to filter events based on the tracing policy. However, the filter was only appled to `kprobe` events. This patch extends the filter to support all events types: `kprobe`, `tracepoint`, `uprobe` and `lsm`. Signed-off-by: Justin Chen <[email protected]>
In cilium#1867, the `--policy-names` flag was added to filter events based on the tracing policy. However, the filter was only appled to `kprobe` events. This patch extends the filter to support all events types: `kprobe`, `tracepoint`, `uprobe` and `lsm`. Signed-off-by: Justin Chen <[email protected]>
In #1867, the `--policy-names` flag was added to filter events based on the tracing policy. However, the filter was only appled to `kprobe` events. This patch extends the filter to support all events types: `kprobe`, `tracepoint`, `uprobe` and `lsm`. Signed-off-by: Justin Chen <[email protected]>
This PR extends the list of filters by implementing the policy name filter. This allows Tetragon to filter events based on the name of a tracing policy.
It also improves Tetragon's docs(see #1965) and extends test suites as needed.Closes #1855