RUN-781 | feat: add sched_process_exec tracepoint as a fallback for older kernels#50
Merged
Conversation
d893b80 to
245e240
Compare
edeNFed
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR aims to expand the kernel matrix we support - specifically targeting RHEL7.9 (kernel 3.10 with patched eBPF functionality). For these kernels:
sys_enter_execverand thesys_exit_execvetracepoints are not supported./proc/<pid>/statusfile don't contain that info on these kernels.To support this, adding a fallback for
sched_process_exectracepoint which is present on these old kernels as well. This fallback is limited in the sense that we don't have direct access to the exec arguments like env vars - and some filtering that we do on the main path are not supported on this mode - this is indicated by a warning log.