Configuration

Qtap offers two flexible management approaches, catering to different deployment needs and preferences: through a cloud control plane or via local configuration files. Both methods provide powerful capabilities with different advantages.

Cloud-Connected Configuration

Cloud-connected mode leverages Qpoint's control plane for centralized management:

• Setup: Register agents with a token from the Qpoint dashboard

• Management: Configure via the web UI or API

• Updates: Changes automatically propagate to agents

• Monitoring: View agent status and health in real-time

# Example: Deploy with cloud-connected configuration
docker run \
  --privileged \
  --pid=host \
  --network=host \
  -v /sys:/sys \
  us-docker.pkg.dev/qpoint-edge/public/qpoint:v0 \
  tap \
  --registration-token=YOUR_TOKEN

Local Configuration

Local configuration mode uses a YAML file for direct agent configuration:

• Setup: Create a qpoint.yaml file with your desired settings

• Management: Update the configuration file and restart the agent

• Control: Complete control over all aspects without external dependencies

• Isolation: Works in air-gapped or restricted environments

# Example: Minimal local configuration
version: 2
services:
  event_stores:
    - id: console_stdout
      type: stdout
  object_stores:
    - id: minio
      type: s3
      endpoint: 127.0.0.1:9000
      bucket: qpoint
      # Additional settings...

stacks:
  default_stack:
    plugins:
      - type: debug
        config:
          mode: summary

tap:
  direction: egress
  http:
    stack: default_stack

Key Configuration Components

A complete Qpoint configuration consists of four key areas, each controlling different aspects of the agent's behavior:

Service Configurations

Define where and how Qtap stores the data it captures:

• Event Stores: Handle metadata about connections (timestamps, bandwidth, endpoints)

• Object Stores: Store actual payload content (headers, bodies)

Stacks & Plugins

Configure how Qtap processes the traffic it observes:

• Stacks: Named collections of plugins that process traffic

• Plugins: Individual processors like error detection, debugging, and usage reporting

Traffic Capture Settings

Control what traffic Qtap monitors:

• Direction: Choose what traffic to capture (ingress, egress, both)

• Filters: Include or exclude specific process groups

• Network Settings: Configure network-related options

Endpoint-Specific Rules

Apply different processing to specific domains or endpoints:

• Domain Mapping: Associate domains with specific processing stacks

• Custom Handling: Apply specialized processing to important services