Configuration
Configure and manage your Qplane deployment. The cloud control plane provides centralized configuration for all connected Qtap agents across your organization.
How Qplane Configuration Works
In cloud-connected mode, your Qtap agents connect to Qplane at app.qpoint.io to receive their configuration. Key principles:
Organization-wide configuration: Stacks, plugins, routing rules, and filters apply to all installations within an organization
Real-time updates: Changes propagate to connected agents within a minute
No restarts required: Agents apply new configuration automatically
Environment identification: Use installations to identify different environments (prod, staging, dev)
Configuration Topics
Structure your Qplane deployment using organizations, installations, and role-based access control.
Learn how to:
Organize your deployment (organizations vs installations)
Use RBAC roles to control team access
Implement multi-environment strategies
Choose the right access control pattern
Best for: Admins setting up team access and organizational structure
Configure how Qtap processes captured traffic using stacks and plugins.
Learn how to:
Create stacks for different traffic types
Configure plugins (Report Usage, Detect Errors, Access Logs, Qscan)
Set up domain-specific routing rules
Use the Reliability dashboard for error detection
Best for: Engineers configuring traffic capture and processing
Manage global settings, storage services, filters, and agent configuration.
Learn how to:
Configure traffic direction (egress-only in Qplane, ingress/all requires local YAML)
Set up object stores (S3, MinIO) for sensitive data
Filter out noisy processes
Manage installations and registration tokens
Best for: Operations teams managing infrastructure and data storage
Set up real-time alerts for API performance, reliability, and security events.
Learn how to:
Create alerting rules (critical latency, root user, vendor availability)
Configure integrations (webhooks, Slack, PagerDuty)
Filter alerts to reduce noise
Review alert events and history
Best for: SREs, Secops, and on-call teams monitoring production traffic
Understand the complete Qpoint architecture and how all the pieces connect.
Learn about:
Data flow (events vs objects vs Qscan)
YAML configuration vs Qplane UI
Plugin architecture and processing pipelines
Control plane vs data plane responsibilities
Best for: Technical leads and architects understanding the full system
Quick Start
1. Already have agents deployed?
Start with Organizations & Environments to structure your deployment
Then configure Stacks & Plugins for traffic processing
2. Need to configure data storage?
Go to Settings to set up S3-compatible object storage
3. Want to set up monitoring?
Jump to Alerting to configure rules and integrations
4. Understanding the system?
Read How It Fits Together for the complete picture
Common Configuration Tasks
Configure S3 storage for sensitive data:
Navigate to Settings → Deploy → Services
Add an S3-compatible object store (MinIO, AWS S3, GCS)
Configure access credentials
See Settings for details
Create a custom stack for specific traffic:
Navigate to Plugins → Stacks
Create a new stack with desired plugins
Set up routing rules to assign domains to your stack
See Stacks & Plugins for details
Set up team access control:
Decide on your organization structure
Invite team members with appropriate roles
Create views for granular filtering (optional)
See Organizations & Environments for details
Configure error alerting:
Navigate to Alerting → Rules
Create or enable alerting rules
Configure webhook/Slack integrations
See Alerting for details
Related Documentation
Installation - Deploy additional Qtap agents
Getting Started - First-time setup walkthrough
Guides - Step-by-step tutorials
Last updated