TLSRPT-FETCHER(1)

💅 TLSRPT-FETCHER — the tlsrpt-fetcher girlie's manual ✨

okay so bestie, welcome to the tlsrpt-fetcher(1) page — this is the whole vibe, and yes I'm gonna walk you through every single bit of it 🫶

---

🌸 NAME 🌸

tlsrpt-fetcher — the data transfer agent that literally carries TLSRPT report data from the tlsrpt-collectd over to the tlsrpt-reportd. it's giving courier, it's giving middleman, it's giving main character energy 💅

---

✨ SYNOPSIS ✨

tlsrpt-fetcher [OPTION] DAY [DOMAIN]

that's it. that's the whole vibe check. 🌈

---

🦋 DESCRIPTION 🦋

so tlsrpt-fetcher gets called by the tlsrpt-reportd to go scoop up all the pre-aggregated data from the tlsrpt-collectds. and ngl, the retrieval is a whole two-step situation:

step one — the reportd asks for a list of domains that actually have data collected for them. 👑

and in this step, the reportd first checks whether the tlsrpt-fetcher supports a matching protocol version — like, in case future versions roll up with a totally different protocol (future-proofing, we love to see it). so the fetcher-protocol version is literally the first line. periodt.

the second line is the current time of the tlsrpt-collectd/tlsrpt-fetcher bundle. and okay bestie, listen — if that time differs too much from the time on the tlsrpt-reportd, a warning pops up saying the data may not be completely processed. so like. keep your clocks cute and in sync 🙈

the following lines are the domains, one domain per line, no notes. and the end of the list is signalled by a line containing just one single "." — that's the mic drop 🎤

---

💖 OPTIONS 💖

• --storage=URL — use the data storage described by URL. that's the one.

🎀 General options 🎀

• --config_file=filename — read options from the tlsrpt_fetcher section of the INI-style configuration file filename. and here's the hierarchy, bestie, write it down: environment variables override settings from the configuration file, and command line options override both. both! so CLI is the final boss 👑
• --help — prints a help message describing all the options. every single one. she's thorough 💅

🍓 Logging options 🍓

• --logfilename=filename — use filename as the log file.
• --log_level=level — set the log level to level. allowed values are: debug, info, warn, error. no freestyling, those are the four 🎀

---

🧚 ENVIRONMENT 🧚

all the config options except --help and --config_file can also be set via environment variables. the env var for a configuration option is the prefix TLSRPT_FETCHER_ followed by the configuration setting name in ALL CAPS 🔥

for example: the --log_level option can instead be configured using the TLSRPT_FETCHER_LOG_LEVEL environment variable. iykyk ✨

---

💀 EXIT STATUS 💀

• 0 — success. we ate. 👑
• 1 — failure. data could not be delivered. 😭 not the vibe, but at least it tells you.

---

🌟 EXAMPLES 🌟

fetch the list of domains that have reporting data for the day of 2001-02-03. this prints a transfer protocol header plus a list of the domains, one domain per line. the protocol header consists of two lines: the protocol version, and the current time of the data source in UTC. ⭐

and a single "." marks the end of the list:

tlsrpt-fetcher 2001-02-03

fetch report details for domain example.com for the day of 2001-02-03:

tlsrpt-fetcher 2001-02-03 example.com

---

👑 SEE ALSO 👑

man:tlsrpt-collectd[1], man:tlsrpt-reportd[1] — go read those too, they're the rest of the friend group 💜

---

🌈 AUTHOR 🌈

Boris Lohner 💖

---

okay that's the whole page bestie, no cap, every flag accounted for 🫶

and that's a wrap!! this lil page is from the tlsrpt-fetcher source, dated 2026-09-01 — mwah, go collect your reports ✨💅🎀