Clusters

e.g. [ "app.host1.com:8080", "app.host2.com:8080", "app.host3.com:8080" ]

The admin application will automatically append weight=1 to each server in the list to distribute the load equally. Behind the scenes, the admin application will also configure a sticky session with a cookie named OMG_backend_{uuid}. When the logout path for any configured application is accessed, all cookies that start with OMG_backend_ will be cleared.

• type - protocol for the healthcheck requests http or https

• http_req - raw http healthcheck request (e.g. GET /status HTTP/1.0\r\nHost: foo.com\r\n\r\n). Replace /status with the URI for your status endpoint.

• interval - The time interval (in milliseconds) between consecutive health check requests (e.g. 10000). 

• timeout - The maximum time (in milliseconds) to wait for a response before considering the health check failed (e.g. 1000). 

• fall - The number of consecutive failed health checks required to mark the endpoint as unhealthy (e.g. 3).

• rise - The number of consecutive successful health checks required to mark the endpoint as healthy (e.g. 2).

• ssl_verify - Specifies whether to enforce SSL certificate verification for HTTPS health check requests (true or false boolean value).