-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
tetragon: Move procevents.GetRunningProcs call from base sensor load #3097
Conversation
24984fc
to
3f0107e
Compare
We need to call procevents.GetRunningProcs after server is started observer listeners are configured. Currently it's called within base sensor load, but it's now loaded before server is started, so we don't get any initial exec events. Fixes: a5d7f0e ("tetragon: Load initial sensor via sensor manager") Signed-off-by: Jiri Olsa <jolsa@kernel.org>
3f0107e
to
3d3213b
Compare
Execute tetragon through main and make sure we get exec events generated. Signed-off-by: Jiri Olsa <jolsa@kernel.org>
3d3213b
to
75167f5
Compare
tus.LoadSensor(t, base.GetInitialSensor()) | ||
tus.LoadInitialSensor(t) | ||
|
||
if err := procevents.GetRunningProcs(); err != nil { |
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.
Do we need that here? It seems that tus.LoadInitialSensor(t)
also calls procevents.GetRunningProcs()
.
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.
ugh, leftover, will remove, thanks
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.
Other than a small comment, this LGTM!
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!
We need to call procevents.GetRunningProcs after server is started observer listeners are configured.
Currently it's called within base sensor load, but it's now loaded before server is started, so we don't get any initial exec events.