query

The query subcommand executes a SQL-like query against transaction logs and joins the results with per-transaction statistics, outputting to CSV.

Note: This tool is experimental and still in incubation.

Usage

rumi tools txnstats query [options]

Options

Option	Description
-l, --log <file>	(Required) Path to the main recovery transaction log
-q, --query <sql>	(Required) SQL-like query to execute
-o, --output <file>	Output CSV file (default: txnstats.csv)
-m, --include-message-logs	Include inbound/outbound message logs in query (default: true)

Prerequisites

The query command expects these related log files in the same directory as the main log:

File	Description
<name>.log	Main recovery transaction log
<name>.txnstats.log	Per-transaction statistics log
<name>.in.log	Inbound message log (optional)
<name>.out.log	Outbound message log (optional)

Example

rumi tools txnstats query \
  -l /path/to/myapp.log \
  -q "SELECT simpleClassName, timestamp FROM logs WHERE timestamp BETWEEN 'today at 3pm' AND 'today at 3:05pm'" \
  -o results.csv

The output CSV will contain:

• Fields selected in the query

• Transaction timing statistics joined by transaction ID

• Inbound and outbound message timing details (when applicable)

Compatibility

3.x Compatibility: For logs created with Rumi 3.x, use the --3x flag before the command:

rumi --3x tools txnstats query -l /path/to/myapp.log -q "SELECT * FROM logs"

See Also

• txnstats - Transaction stats tools overview

• txnstats dump - Dump transaction stats to CSV

• Configuring Per-Transaction Statistics - How to enable per-transaction stats logging

• Querying Transaction Logs - Understanding the query syntax