hpct-query(1)

📦
version 2.2.10 · 2 versions
, in ubuntu stonking

💖 hpct-query(1) — HiPerConTracer Query Tool 💖

okay bestie, this is a page from the General Commands Manual, so you know it's the real deal. hpct-query is your little ride-or-die that goes digging in a HiPerConTracer database for Ping or Traceroute results. Let's get into it 💅

✨ NAME ✨

hpct-query — HiPerConTracer Query Tool

🦋 SYNOPSIS 🦋

hpct-query database_configuration ping|traceroute
           [-L level | --loglevel level]
           [-Z on|off | --logcolor on|off]
           [-O file | --logfile file]
           [-q | --quiet] [-w | --verbose]
           [-o filename | --output filename]
           [-T table_name | --table table_name]
           [-V version | --table-version version]
           [-M mapping_file | --address-to-measurementid mapping_file]
           [--deduplication on|off]
           [--from-time timestamp] [--to-time timestamp]
           [--from-measurement-id measurement_identifier]
           [--to-measurement-id measurement_identifier]
hpct-query [-h | --help]
hpct-query [-v | --version]

🌸 DESCRIPTION 🌸

So basically, hpct-query gives you one simple query command to query a HiPerConTracer database for Ping or Traceroute results inside a given time range. The output format is the same as the uncompressed HiPerConTracer results format — no glow-up, no remix. (The HiPerConTracer manpage has the full format description if you wanna go read it, iykyk.)

🎀 ARGUMENTS 🎀

Here's everything you can hand it, bestie:

  • database_configuration — the database configuration file. That's the one you pass first, no skipping it.
  • ping|traceroute — which flavour of data you wanna query: traceroute or ping. Pick your fighter ✨
  • -L level | --loglevel level — sets the minimum logging level to whatever value you gave it. The scale is: 0=trace, 1=debug, 2=info, 3=warning, 4=error, 5=fatal.
  • -Z on|off | --logcolor on|off — turns the use of ANSI color escape sequences on (on) or off (off) so your log output gets colourised based on its level. Aesthetic logging, we love to see it 🌈
  • -O file | --logfile file — sets a file name to append the log output to. Heads up: if you set a file, no log output goes to the console. If you don't, all the log output goes to the console. Pick a lane 🫶
  • -q | --quiet — sets the minimum logging level to 3 (warning). Shhh 🤫
  • -w | --verbose — sets the minimum logging level to 0 (trace). Not me wanting every single detail 💀
  • -o filename | --output filename — sets the specified filename as the output file. The extensions .gz, .bz2, and .xz are recognised so compression gets enabled. Slay ✨
  • -T table_name | --table table_name — sets a custom table name to query from.
  • -V version | --table-version version — sets the table version (default is: 2). You'd use this option to read a table from an older HiPerConTracer schema version. Throwback vibes 🕰️
  • -M mapping_file | --address-to-measurementid mapping_file — sets a mapping file containing space-separated IP address to measurement ID mappings, one mapping per line. Where the measurement ID is zero, the measurement ID gets looked up from the mappings. You can use this option to later map measurements to a useful measurement ID for export. Example mapping file contents:
1.2.3.4 1000
3ffe::1:2:3 1000
5.6.7.8 2222
2001::1:2:3 2222
 ...
  • --deduplication on|off — performs deduplication of the output. This one is for debugging, or for handling badly misconfigured database schemata where the primary index is non-unique. In almost all cases this option is unnecessary and should be turned off. Default: off. Like, fr fr, leave it off 🙈
  • --from-time timestamp — sets the beginning of the time range as a string in the format "%Y-%m-%d %H:%M:%S.%F". If you don't provide it, all results get queried.
  • --to-time timestamp — sets the end of the time range as a string in the format "%Y-%m-%d %H:%M:%S.%F". If you don't provide it, all results after a given from-time get queried.
Note: data at the to-time timestamp is not included in the export — only time stamps less than to-time! So the time interval for export is [from-timestamp, to-timestamp). This is so you can, for example, export daily batches without having the same value show up in two files. Iconic design choice tbh 👑
  • --from-measurement-id measurement_identifier — sets the beginning of the measurement identifier range. If you don't provide it, all results get queried.
  • --to-measurement-id measurement_identifier — sets the end of the measurement identifier range. If you don't provide it, all results get queried.
  • -h | --help — prints command help.
  • -v | --version — prints program version.

💜 EXIT STATUS 💜

The hpct-query tool exits with 0 on success, and >0 in case of an error. That's it, that's the vibe check 🌟

🔥 EXAMPLES 🔥

hpct-query hipercontracer-database.conf ping

hpct-query hipercontracer-database.conf traceroute

hpct-query hipercontracer-database.conf ping --from-time 2022-09-29 13:00:00

hpct-query hipercontracer-database.conf traceroute --from-time 2022-09-29 00:00:00 --to-time 2022-09-29 12:00:00

hpct-query hipercontracer-database.conf traceroute --from-measurement-id 1000 --to-measurement-id 2000

hpct-query hipercontracer-database.conf traceroute --from-measurement-id 1000 --to-measurement-id 2000 --output results.xz

hpct-query hipercontracer-database.conf ping --table test_ping_table

hpct-query hipercontracer-database.conf traceroute -T Traceroute_v1 -V 1 --from-time 2015-10-16 --to-time 2015-10-17 -o Traceroute-2015-10-16.hpct.xz -M addressmappings.txt

hpct-query --version

hpct-query -h

🧚 NOTES 🧚

This program is part of HiPerConTracer. The latest version of HiPerConTracer can be found on the HiPerConTracer Homepage at HiPerConTracer Homepage: https://www.nntb.no/~dreibh/hipercontracer/. Go peek, bestie 🦋

👑 AUTHORS 👑

Thomas Dreibholz, Homepage: https://www.nntb.no/~dreibh

And that's the whole page, bestie — hpct-query, from the hpct-query(1) manual, dated May 26, 2026, version hpct-query(1). Periodt. 💅✨

📦 where this page comes from