TRACERTSTATS(1)

✨ tracertstats ✨

okay bestie, come sit with me 💖 this is the tracertstats(1) page — it lives in the User Commands section of the manual, and it's literally just vibes + packet counting, no cap.

---

🎀 NAME 🎀

tracertstats — do a lil simple filter-based analysis on a trace 🦋

---

🌸 SYNOPSIS 🌸

tracertstats [ -f | --filter bpf ] [ -i | --interval interval ] [ -c |
--count count ] [ -o | --output-format csv,txt,png,html ] [ -m |
--merge-inputs ] inputuri...

tracertstats -H|--libtrace-help

yes queen, two whole invocation forms, we love a flexible icon 💅

---

💜 DESCRPTION 💜

okay so tracertstats takes a whole list of bpf expressions and then, every interval seconds (or every count packets), tells you the number of packets and bytes that matched each expression. it's giving "live scoreboard but for network traffic" 📊✨

yes, the heading says DESCRPTION, not DESCRIPTION. that's the original's spelling and we are respecting the lore, not fixing it. 💀

• -f bpf-filter, --filter bpf-filter — add another "bpf filter". stack as many as your heart desires 🫶
• -i interval, --interval interval — spit out results every interval seconds ⏰
• -c count, --count count — spit out results every count packets 🔢
• -m, --merge-inputs — treats all the inputs as one single input, so you get one unified output instead of one output per input. works best with traces that are consecutive, so you can smash them into a single CSV for instance. chef's kiss 🤌
• -o format, --output-format format — picks the output format, bestie. options are:
  • txt — human readable text. this is the default output format and it's easy for a human to understand. downside? it takes up quite a bit of horizontal space 😭 (wide girl energy)
  • csv — Comma Seperated Values. perfect if you wanna do more analysis in a spreadsheet or some other program 📈
  • png — PNG Graphic. produces a fairly incomprehensible png graph 💀 and it relies on gdc being available at compile time, so it's not always gonna show up for you. no cap.
  • html — output that's suitable for displaying to a human in a webbrowser 🌈

---

🍓 EXAMPLES 🍓

here's the moment you've been waiting for, bestie — look at this stack of filters go:

tracertstats --filter 'host sundown' \
     --filter 'port http' \
     --filter 'port ftp or ftp-data' \
     --filter 'port smtp' \
     --filter 'tcp[tcpflags] & tcp-syn!=0' \
     --filter 'not ip' \
     --filter 'ether[0] & 1 == 1' \
     --filter 'icmp[icmptype] == icmp-unreach' \
     --output-format html
     erf:/traces/trace1.gz \
     erf:/traces/trace2.gz

eight filters, two erf traces, html out. it's giving main character. periodt 💅🔥

---

🧚 LINKS 🧚

wanna know more details about tracertstats (and libtrace)? go here, iykyk:

http://www.wand.net.nz/trac/libtrace/wiki/UserDocumentation 🌐

---

👑 SEE ALSO 👑

libtrace(3), tracemerge(1), tracesplit(1), tracesplit_dir(1), tracefilter(1), traceconvert(1), tracereport(1), tracepktdump(1), traceanon(1), tracesummary(1), traceconvert(1), tracereplay(1), tracediff(1), traceends(1), tracetopends(1)

(yep, traceconvert(1) is in there twice — iconic of it honestly, we leave it exactly as it is 🫶)

---

💖 AUTHORS 💖

Perry Lorier <perry@cs.waikato.ac.nz> — ty for your service, legend 🫡✨

---

and that's the whole page bestie!! this little beauty is part of tracertstats (libtrace), dated November 2006 — yes, 2006, she's vintage and she still ate 💅🌸 go count some packets, you got this 🦋💖