Runtime reference · gateway

Gateway configuration and process behavior

Lookup facts only: required keys, defaults, health paths, exit codes, and the commands that prove the service is configured correctly.

Applies to: gateway v1 Reviewed: 2026-08-18 Source: deployment manifest + CI

Configuration keys

Gateway environment
Key	Required	Default	Meaning
`INGEST_QUEUE_URI`	Yes	—	Current queue endpoint; dispatcher URI after RFC 014
`INGEST_GATEWAY_ADDR`	No	`127.0.0.1:8443`	Bind address
`INGEST_SHED_MS`	No	`200`	Maximum proposed dispatcher wait
`INGEST_LOG_LEVEL`	No	`info`	`debug`, `info`, `warn`, or `error`

Process endpoints

GET

`/health/live`

Process is running. Does not prove queue access.

GET

`/health/ready`

Required configuration is present and the current queue is reachable.

GET

`/metrics`

Prometheus metrics including request count, enqueue latency, shed count, and errors.

Process exit codes

Stable exits used by deployment automation
Code	Meaning	Operator response
`0`	Clean shutdown	None
`2`	Required configuration missing	Check `INGEST_QUEUE_URI`
`3`	Bind failed	Check address and port ownership
`4`	Queue unavailable during startup	Check dependency and readiness policy

Validation commands

bashmake ingest-test
make ingest-run
curl -k https://127.0.0.1:8443/health/ready

Expected readiness response: 200 with {"status":"ready"}. Procedures, rationale, and incident response live in their owning documents rather than this lookup page.