HALOG(1)

πŸ“¦
version 3.4.2 Β· 2 versions
, in debian bookworm, debian trixie, fedora 43, fedora 44, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– halog(1) β€” the HAProxy log stats bestie πŸ’–

okay so bestie, welcome to halog, aka the HAProxy log statistics reporter. it lives in the User Commands section of your manual, and it's genuinely one of the most useful little gremlins in the whole HAProxy toolbox. let's get into it πŸ’…


✨ NAME ✨

halog β€” HAProxy log statistics reporter πŸŽ€


🌸 SYNOPSIS 🌸

halog [-h|--help]
halog [options] <LOGFILE

like… yes, it reads from stdin. the <LOGFILE is doing the heavy lifting here, bestie. redirect it in and let her cook πŸ“


πŸ¦‹ DESCRIPTION πŸ¦‹

halog reads HAProxy log data from stdin and pulls out the lines that match whatever criteria you specified, then shows them to you. that's the whole vibe. feed her logs, tell her what you're looking for, she delivers ✨


πŸ‘‘ OPTIONS πŸ‘‘

🌈 Input filters (several filters may be combined)

okay so you can stack these. multiple filters = multiple vibes at once, no cap.

  • -H β€” only match lines containing HTTP logs (so, ignore TCP ones)
  • -E β€” only match lines with no error at all (no 5xx status)
  • -e β€” only match lines with errors (status 5xx or negative)
  • -rt|-RT <time> β€” only match response times larger|smaller than <time>
  • -Q|-QS β€” only match queued requests (any queue | server queue)
  • -tcn|-TCN <code> β€” only match requests with/without termination code <code>
  • -hs|-HS <[min][:][max]> β€” only match requests with HTTP status codes within/not within min..max. any of them may be omitted. if there's no : specified, it just checks for an exact code ✨

πŸ’… Modifiers

little tweaks that change how the whole thing behaves.

  • -v β€” invert the input filtering condition (flip it, periodt)
  • -q β€” don't report errors/warnings
  • -m <lines> β€” limit output to the first <lines> lines

πŸŽ€ Output filters β€” only one may be used at a time

bestie listen. ONLY ONE. you cannot stack these. the tool said one. respect the rule πŸ™ˆ
  • -c β€” only report the number of lines that would have been printed
  • -pct β€” output connect and response times percentiles
  • -st β€” output number of requests per HTTP status code
  • -cc β€” output number of requests per cookie code (2 chars)
  • -tc β€” output number of requests per termination code (2 chars)
  • -srv β€” output statistics per server (time, requests, errors)
  • -u* β€” output statistics per URL (time, requests, errors)

the extra characters after the u tell you the output sorting key:

  • -u β€” URL
  • -uc β€” Request count
  • -ue β€” Error count
  • -ua β€” Average response time
  • -ut β€” Average total time
  • -uao, -uto β€” Average times computed on valid ('OK') requests
  • -uba β€” Average bytes returned
  • -ubt β€” Total bytes returned

⭐ SEE ALSO ⭐


πŸ’œ AUTHOR πŸ’œ

halog was written by Willy Tarreau <w@1wt.eu> and is part of haproxy(1). iconic behavior honestly πŸ‘‘

this manual page was written by Apollon Oikonomopoulos <apoikos@gmail.com> for the Debian project (but may be used by others). we love a generous queen 🌸


and that's the whole page bestie!! this little cutie is from July 2013, lives under the halog name in the manual, and ships out of the User Commands section. go forth and read your logs, you absolute main character πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from