metrics: add a per-exec-id counter for missing parents #24
Conversation
This file contains 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
This counter is useful to help debug cases where process exec events are missing a parent. Using the parent exec ID in the metric, we can determine the corresponding pid and cross check against Tetragon event logs. This can help establish patterns and determine an underlying root cause. As a practical example, this counter recently helped me diagnose the underlying cause of missing parents in kind deployments. Signed-off-by: William Findlay <[email protected]>
willfindlay
force-pushed
the
pr/willfindlay/missing-parent-metrics
branch
from
ca449fb to
2ca9b66
Compare
kkourt
approved these changes
May 16, 2022
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 counter is useful to help debug cases where process exec events are missing a parent.
Using the parent exec ID in the metric, we can determine the corresponding pid and cross
check against Tetragon event logs. This can help establish patterns and determine an
underlying root cause.
As a practical example, this counter recently helped me diagnose the underlying cause of
missing parents in kind deployments.
Signed-off-by: William Findlay [email protected]