What Just Ran on My Server?
A short-lived process changes the system, then disappears before snapshot-based monitoring sees it.
syscalls/sys_enter_execveSeven incident-first labs for engineers who operate Linux. Reproduce one bounded failure, collect one useful signal, and learn exactly where the evidence ends.
THE INCIDENT QUEUE
Every lab starts with an operational question. Hosted badges describe what runs here today.
A short-lived process changes the system, then disappears before snapshot-based monitoring sees it.
syscalls/sys_enter_execveA service repeatedly looks for configuration, but ordinary logs omit the pathname or return code.
sys_enter_openat + sys_exit_openatA client cannot connect, but the failure disappears inside generic application telemetry.
sys_enter_connect + sys_exit_connectA request is slow and DNS is suspected without a measured resolver boundary.
resolve_backend uprobeLatency coincides with packet loss, but averages hide the affected flows.
tcp/tcp_retransmit_skbContainer and host process identifiers appear to contradict each other.
sys_enter_execve + /proc enrichmentA program that looks correct fails before attachment at the kernel verifier boundary.
syscalls/sys_enter_write + CO-RETHE METHOD
Each fixture creates a controlled failure. It is a teaching environment, never a production claim.
The observer attaches to a named kernel boundary and emits typed, time-bounded events.
A learner completes the incident only after naming what the evidence cannot establish.
PUBLIC ROADMAP
Execution, file access, and verifier portability with fixed operations.
ARM64 and additional distribution kernels with observed compatibility receipts.
Operator workshops, translations, and reviewed contributor incidents.