Where Does SIPp Store Scenarios and Logs?
SIPp writes scenarios, logs and stats to the working directory with flag-selected names. No fixed data dir exists.
Last updated
SIPp is working-directory software with flags for everything. Scenarios arrive per run with embedded fallbacks dumpable on demand. Logs fan out by trace type with scenario-prefixed names.
Pcap and CSV inputs resolve relative to invocation with privilege needs noted. No installed paths exist beyond build-time choices. Quote flags plus working dir, never fixed trees.
Where SIPp stores this, by platform
<working-dir>/
Scenario XML plus per-trace logs and stats land in the invocation directory with scenario-prefixed names. Embedded fallbacks dump on demand. No installed data dir exists by design; this entry names the working dir itself.
Frequently asked questions
Where are SIPp log files?
They land in the working directory with scenario-prefixed names per trace flag. Messages, errors, counts and stats each take flag-gated files. Ring buffers rotate with epoch names.
Where are SIPp scenario files?
Supply XML paths per run with embedded fallbacks dumpable on demand. Injection CSVs and pcap paths ride alongside per invocation. No installed scenario library exists to quote.
How do pcap paths work in SIPp?
They resolve relative to invocation with root needs for capture. CSV rows feed calls per file. Build flags gate SSL and capture support.
Notice an outdated path? Let us know.