connection-status

Use the connection-status { ... } block to monitor each RADIUS backend connection independently with Status-Server requests.

backends {
    radius "UPSTREAM" {
        server "PRIMARY" {
            secret "mysecret";
            timeout 3s;

            connection-status {
                interval 10s;
                timeout 3s;
                max-timeouts 3;
            }

            connect {
                protocol tcp;
                host "primary.example.com";
                port 1812;
            }
        }
    }
}

Each parameter is required. The block is also available in a radius-dns-sd server-template.

Each connection has its own polling schedule and consecutive timeout count. Radiator sends at most one Status-Server probe at a time over that exact connection. A valid response resets the count. When the count reaches max-timeouts, Radiator closes only that connection. Timeout counts for other connections are unaffected.

Polling starts when the pool opens a connection.

For TCP and TLS, a connection is one stream. For UDP, it is one connected backend socket.

Parameters

interval

Delay between completing one probe and sending the next probe.

timeout

Maximum time to wait for a valid Status-Server response.

max-timeouts

Number of consecutive probe timeouts after which Radiator closes the connection. Must be at least 1.

Availability and SLO impact

Probe results do not directly affect the server-level service-level objective. Closing a connection can reduce service availability, especially if all connections close. When the number of connections falls below the configured min, Radiator attempts to open replacement connections.

Compatibility syntax

The boolean status statement remains supported. status true; uses a 10s interval, the server's timeout, and a max-timeouts value of 1. status false; disables polling. Do not configure both forms in the same server or server template.