/usr/bin/varnishlog-json --help — Chainguard OS Manuals

From varnish 9.1.0-r3 (os), captured 2026-11-05 by running varnishlog-json --help (exit 1). permalink

/usr/bin/varnishlog-json: invalid option -- '-'
Usage: /usr/bin/varnishlog-json <options>

Options:
 [-a]                      Append to file
 [-b]                      Only display backend records
 [-c]                      Only display client records
 [-C]                      Caseless regular expressions
 [-d]                      Process old log entries and exit
 [-D]                      Daemonize
 [-E]                      Display ESI transactions
 [-g <probe|request|vxid>] Grouping mode (default: vxid)
 [-h]                      Usage help
 [-i <taglist>]            Include tags
 [-I <[taglist:]regex>]    Include by regex
 [-k <num>]                Limit transactions
 [-L <limit>]              Incomplete transaction limit
 [-n <workdir>]            varnish working directory
 [-p]                      Pretty-print
 [-P <file>]               PID file
 [-Q <file>]               VSL query file
 [-q <query>]              VSL query
 [-r <filename>]           Binary file input
 [-R <limit[/duration]>]   Output rate limit
 [-t <seconds|off>]        VSM connection timeout
 [-T <seconds>]            Transaction end timeout
 [-V]                      Version
 [-w <filename>]           Output filename
 [-x <taglist>]            Exclude tags
 [-X <[taglist:]regex>]    Exclude by regex

Options (11)

Option	Description	Source
`-a`	When writing output to a file with the -w option, append to it rather than overwrite it.	man
`-b`	Only display transactions and log records coming from backend communication.	man
`-c`	Only display transactions and log records coming from client communication.	man
`-C`	Do all regular expression and string matching caseless.	man
`-d`	Process log records at the head of the log and exit.	man
`-D`	Daemonize.	man
`-E`	Display ESI transactions and other types of sub-requests.	man
`-h`	Print program usage and exit	man
`-p`	Pretty-print transactions rather than using NDJSON	man
`-V`	Print version information and exit.	man
`--optstring`	Print the optstring parameter to getopt(3) to help writing wrapper scripts.	man

Examples (7) from the manual page, untested

varnishlog-json
Display client transactions in real time:
varnishlog-json -b -p
Display backend transactions with pretty-printing:
varnishlog-json -D -w /var/log/varnish/json.log -P /run/varnishlog-json.pid
Log client requests to a file in daemon mode:
varnishlog-json -q 'ReqURL eq "/api/health"'
Filter requests for a specific URL:
varnishlog-json -g request
Display request groups (client + related backend transactions):
varnishlog-json -g probe
Display backend health probe results:
varnishlog-json -r /var/log/varnish/raw.log
Read from a binary log file:

Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.