The situation where syscall events are lost when tracing programs with frequent system calls.

Open
#2,049 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, linux
Domain
observability, operating-systems

Research direction

Start by tracing how sysdig captures syscall events and where its ring-buffer size is configured; the issue provides no file or test names. Reproduce capture with a program making frequent system calls, compare the live capture with the saved event file, and document or implement a configuration path if supported.

Written by the indexing model from the issue text.

Description

difficulty-easy feature-request pinned

I captured system call events of a container using sysdig and saved the events to a file. In my subsequent analysis, I noticed that some events were missing. I'm wondering if this might be due to sysdig not being configured with an appropriate ring buffer size when it was started, resulting in event loss. Can sysdig be configured to modify the ring buffer size?

Dominant language
C++
Stars
8.3k
Forks
753
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from draios/sysdig

All issues in draios/sysdig

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.