BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//conference.wireshark.org//sf26eu//talk//USXFHG
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-sf26eu-USXFHG@conference.wireshark.org
DTSTART;TZID=CET:20261105T174500
DTEND;TZID=CET:20261105T184500
DESCRIPTION:Every Linux engineer knows the moment: a process is misbehaving
 \, so you reach for strace\, get a wall of text\, and start grepping. It w
 orks - until the problem spans multiple processes\, the output is too much
  to read\, or you need to correlate what a process did to the system with 
 what it did on the network. strace and bpftrace are excellent at capturing
  syscalls. \n\nStratoshark takes a different approach: it captures system 
 calls and logs system-wide through the Falco libraries\, then hands them t
 o the same analysis engine that has served packet analysts for 25 years 
 — display filters\, coloring rules\, follow-stream views\, time correlat
 ion\, and shareable capture files.\n\nIn this talk I'll show how a Wiresha
 rk user's instincts transfer directly to syscall troubleshooting\, where S
 tratoshark beats reaching for strace\, and where the older tools are still
  the right call. Real debugging scenarios\, honest limitations\, and a cle
 ar picture of when this newer approach earns its place in your toolbox.
DTSTAMP:20261023T232938Z
LOCATION:Ballroom Salon A
SUMMARY:Beyond Strace: Syscall Analysis the Wireshark Way - Roland Knall
URL:https://conference.wireshark.org/sf26eu/talk/USXFHG/
END:VEVENT
END:VCALENDAR