Skip to main content
The print command reads events from a file and displays them to stdout with various formatting options.

Usage

retis print [INPUT] [OPTIONS]

Arguments

INPUT
path
default:"retis.data"
Input file containing stored events.Can be:
  • A single file path (e.g., events.data)
  • A range of rotated files (e.g., events.data[0-5])
If not specified, defaults to retis.data.
retis print events.data
retis print  # Uses retis.data

Options

--format
enum
default:"multi-line"
Format used when printing events.Options:
  • multi-line - Detailed multi-line output (default)
  • single-line - Compact single-line output
retis print --format single-line
retis print --format multi-line
--utc
boolean
Print timestamps as UTC instead of monotonic timestamps.
retis print --utc
-e
boolean
Print link-layer information from packets.
retis print -e

Examples

# Print events from default file
retis print

Output Example

Multi-line format (default)

136852156905 (3) [swapper/3] 0 [k] ip_local_deliver #1fdd03636dffff889641716940 (skb ffff889642506300)
  172.16.42.1.39677 > 172.16.42.2.8080 tos 0x0 ttl 64 id 17803 off 0 [DF] len 31 proto UDP (17) len 3
  ns 0x1/4026531833 if 2 (eth0) rxif 2
  ct_state NEW status 0x100 udp orig [172.16.42.1.39677 > 172.16.42.2.8080]

Single-line format

136852156905 (3) [swapper/3] 0 [k] ip_local_deliver #1fdd03636dffff889641716940 172.16.42.1.39677 > 172.16.42.2.8080

File Types

The print command automatically detects the file type:
  • Event files - Raw events from retis collect
  • Series files - Sorted events from retis sort
Both formats are printed appropriately.

Paging

When output is longer than the terminal height, a pager is automatically used. Control paging behavior:
# Use a specific pager
PAGER=more retis print

# Disable paging
NOPAGER=1 retis print

Common Use Cases

Quick review of captured events

retis print

Search for specific patterns

retis print | grep "tcp port 443"

Export to text file

retis print events.data > output.txt

Compare different captures

retis print before.data > before.txt
retis print after.data > after.txt
diff before.txt after.txt

See Also

  • collect - Collect events
  • sort - Sort events by tracking ID
  • pcap - Generate pcap files

Build docs developers (and LLMs) love