-
Notifications
You must be signed in to change notification settings - Fork 915
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
Frequent syscall event drops #1382
Comments
I'm also experiencing this: Environment
Additional context
|
Please, could you try to increment (or remove) the container CPU limit? N.B. |
@leogr thanks for the suggestion. I tried that
And it doesnt seem to help much, what i noted is that the amount of dropped events is significantly higher after startup time and then it tend to stabilize.
In any case thanks for the reply! is there anything else i can try or look into to try to help you to debug this? |
Since it seems to be not related to CPU performance (unless you noticed that Falco is using 100% of its allocated CPU), I'd suggest looking on those components used by Falco to fetch metadata that might slow down Falco (eg. Kubernetes APIs). For example, are you using PS |
If I understand correctly, there is no |
Hey everyone, I wrote an "umbrella" issue, that can help with debugging this problem, PTAL 👉 #1403 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Issues labeled "cncf", "roadmap" and "help wanted" will not be automatically closed. Please refer to a maintainer to get such label added if you think this should be kept open. |
This is being tracked here #1403 - closing this to keep things clean and avoid duplicates. Thanks to the original reporter @Yuriy6735 for bringing this to our attention. |
Falco generates repeated alerts:
Critical Falco internal: syscall event drop. 1 system calls dropped in last second. (ebpf_enabled=0 n_drops=1 n_drops_buffer=1 n_drops_bug=0 n_drops_pf=0 n_evts=19802)
How to reproduce it
Run Falco 0.25 with EKS 1.15 and centos7
Expected behaviour
No syscall event drop errors
Environment
Falco version: 0.25.0 Driver version: ae104eb20ff0198a5dcb0c91cc36c86e7c3f25c7
Additional context
The text was updated successfully, but these errors were encountered: