onr.yaml file is the master configuration for your ONR gateway. It dictates server ports, file watch reload behaviors, traffic dump controls, and observability settings.
Server Settings
Controls the core HTTP server bounds and process signals.Global Authentication
You can secure the gateway itself by requiring an API key for incoming requests.api_key is set, all clients must send Authorization: Bearer change-me or use a defined key in keys.yaml)
Upstream Forwarding Proxies
If ONR needs to egress traffic through a corporate proxy (like a NAT gateway or a local VPN client like Clash), you can set this universally per provider.Hot Reloads
You can configure ONR to natively watch the.conf DSL files and reload itself safely without dropping inflight requests.
Traffic Dumps (Audit)
If you need to capture raw, unadulterated request/response payloads (for debugging or exact payload auditing), activatetraffic_dump.
Access Logs & Rotation
Access logs provide the core metrics generation for your cluster. System logs are written tostderr with fixed prefix format:
[ONR] <time> | <LEVEL> | <category> | <message> | key=value ...