Configuration Files
Main Configuration File
By default, Proton looks for configuration in:- Docker:
/etc/proton-server/config.yaml - Binary:
./proton-data/config.yamlor specified with--config-file
Configuration Directory Structure
Configuration Format
Proton supports both YAML and XML formats. YAML is recommended for readability:Network Settings
Port Configuration
Configure network ports for different protocols:Listen Host
Control which interfaces Proton binds to:Connection Limits
Storage Configuration
Data Paths
Configure where Proton stores data:Stream Storage Configuration
Configure internal streaming storage:Native Log (Default)
Kafka/Redpanda Integration
Checkpoint Configuration
Query state checkpointing for fault tolerance:Resource Limits
Memory Settings
Query Concurrency
Thread Pools
Logging Configuration
Log Levels and Output
Per-Component Log Levels
Query Logging
Node Roles
Configure which roles the node should perform:TLS/SSL Configuration
Enable HTTPS and Secure TCP
User Configuration
User settings are stored inusers.yaml:
User Profiles
Environment Variables
Override configuration with environment variables (Docker):| Variable | Description |
|---|---|
PROTON_CONFIG | Path to config file |
STREAM_STORAGE_BROKERS | Kafka broker addresses |
STREAM_STORAGE_TYPE | kafka or nativelog |
MAX_CONCURRENT_QUERIES | Query concurrency limit |
MAX_SERVER_MEMORY_USAGE_TO_RAM_RATIO | Memory limit (0-1) |
MAX_SERVER_MEMORY_CACHE_TO_RAM_RATIO | Cache size (0-1) |
Configuration Validation
Check Configuration
Validate your config before starting:Skip Validation
To skip validation of user-level settings in server config:Configuration Best Practices
- Use YAML format for better readability and maintainability
- Store secrets securely - don’t commit passwords to version control
- Set appropriate memory limits based on available RAM
- Enable TLS for production deployments
- Configure log rotation to prevent disk space issues
- Use config.d/ for modular configuration
- Document custom settings in comments
- Test configuration changes in non-production first
Example Complete Configuration
Next Steps
- Monitor your deployment with Monitoring
- Optimize settings with Performance Tuning
- Review Deployment options