Status and config
Daemon-wide status, the resolved running configuration, the runtime log level, and bootstrap config validation. Read-only endpoints plus one mutation for log level and one for validation.
Status
GET /admin/status
Returns proxy state and a summary of the loaded control-plane store.
producers is a boolean indicating whether any producer is registered; producer_counts breaks that down per NF type. filter_count, policy_rules, and rate_limits reflect the currently active filter chain and rules in the control-plane store.
Running config
GET /admin/config
Returns the resolved running configuration as JSON. Secret-bearing fields are redacted. This goes through the same redaction path as d3x-edge -print-config, so the two views can't diverge.
Log level
GET /admin/log-level
Returns the current log level.
PUT /admin/log-level
Change the log level at runtime. Body:
Accepted values: trace, debug, info, warn, error, fatal, panic. The change takes effect immediately. It is held in the running process only — it is node-local (not cluster-wide) and resets to the configured level on restart.
Validate config
POST /admin/config/validate
Validates a full Config bootstrap payload without applying it — useful for checking a YAML or JSON config before a deploy. Send the document as the request body (set Content-Type: application/yaml for YAML; JSON is the default). On success:
On failure, the response carries the validation errors:
Examples