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

kprobe/process: silence verbose warnings + add metrics #37

Merged
merged 2 commits into from
May 18, 2022

Conversation

willfindlay
Copy link
Contributor

@willfindlay willfindlay commented May 18, 2022

There were some very verbose warnings that were inundating the logs. Let's silence them behind a debug flag and add a metric to help with debugging.

Best reviewed by commit.

@willfindlay willfindlay requested review from jrfastab and olsajiri May 18, 2022 15:19
willfindlay and others added 2 commits May 18, 2022 11:28
The event merge warnings were overly verbose and flooding the logs with useless
information. Silence these warnings by putting them behind a debug flag and add a metric
to help track such errors. This patch is loosely based on a previous version by Jiri but
with some additional information in the metrics.

Tested with crds/examples/sys_write_follow_fd_prefix.yaml and it produces metrics like the following:

    isovalent_generic_kprobe_merge_errors{curr_fn="__x64_sys_read",curr_type="enter",prev_fn="__x64_sys_read",prev_type="enter"} 6

Signed-off-by: William Findlay <[email protected]>
Co-authored-by: Jiri Olsa <[email protected]>
This commit silences "read error!" messages when exec id read fails, hides them behind
a debug flag, and adds a metric to count such errors.

Signed-off-by: William Findlay <[email protected]>
@willfindlay willfindlay force-pushed the pr/willfindlay/metrics branch from 41647c9 to 970100f Compare May 18, 2022 15:28
@michi-covalent michi-covalent merged commit 76c33ab into cilium:main May 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants