CLI

This guide covers the essential command-line options for configuring and running Qtap.

Basic Syntax

qtap [flags]

Essential Flags

Configuration

Flag	Description
--config=	Path to the YAML configuration file
--registration-token=	Token for cloud-connected mode

Logging Options

Flag	Default	Description
--log-level=	info	Set logging detail level (debug, info, warn, error)
--log-encoding=	console	Log format (console, json)

TLS Configuration

Flag	Default	Description
--tls-probes=	nodetls,openssl,gotls	TLS libraries to monitor (nodetls,openssl,gotls,javassl)

Other

Flag	Default	Description
-v, --version		Display Qtap version
-h, --help		Display help information

Common Usage Examples

Running with a Local Configuration File

qtap --config=/path/to/qpoint.yaml

Running with Qplane

qtap --registration-token=YOUR_TOKEN

Adjusting Log Level for Troubleshooting

qtap --config=/path/to/qpoint.yaml --log-level=debug

Using JSON Log Format for Structured Logging

qtap --config=/path/to/qpoint.yaml --log-encoding=json

Monitoring Specific TLS Libraries

qtap --config=/path/to/qpoint.yaml --tls-probes=openssl,gotls,javassl

Cloud-Connected with Enhanced Debugging

qtap --registration-token=YOUR_TOKEN --log-level=debug --log-encoding=json

Checking the Qtap Version

qtap --version

TLS Probes Available

Probe	Description
openssl	Monitor OpenSSL traffic
gotls	Monitor Go TLS traffic
nodetls	Monitor Node.js TLS traffic
javassl	Monitor Java SSL/TLS traffic

To monitor multiple libraries, combine them with commas (no spaces):

--tls-probes=openssl,gotls,javassl