http
The HTTP backend enables Radiator to make HTTP requests to external web services for authentication and authorization purposes.
Health Monitoring
Add a service-level-objective block to enable
automatic circuit breaking. When the backend reaches the failure rate, Radiator marks it as
degraded and applies exponential backoff before retrying. See the
Service Level Objective documentation for details.
HTTP backends have no SLO by default — health monitoring is opt-in. When an explicit
service-level-objective block is present, omitted fields use the standard defaults
(failure-rate 3/5, initial-backoff-period 3s, max-backoff-period 30s,
recovery-probe-count 2).
Only infrastructure-level HTTP responses count as failures toward the SLO:
- 5xx — server-side errors (the backend is crashing or misconfigured)
- 429 Too Many Requests — the backend is overloaded or rate-limiting
Application-level responses such as 401 Unauthorized, 403 Forbidden, and
404 Not Found are valid AAA outcomes and do not affect the failure rate.