---
title: Auto-healing for unavailable servers
description: Using gauges, set up auto-healing in a container deployment to address an unavailable server.
component: pingauthorize
version: 11.0
page_id: pingauthorize:pingauthorize_server_administration_guide:paz_auto_healing
canonical_url: https://docs.pingidentity.com/pingauthorize/11.0/pingauthorize_server_administration_guide/paz_auto_healing.html
revdate: July 29, 2022
section_ids:
  steps: Steps
---

# Auto-healing for unavailable servers

Using gauges, set up auto-healing in a container deployment to address an unavailable server.

## Steps

1. Configure one or more of the gauges described in [Server availability](paz_server_availability.html).

2. Configure the gauges to trigger the UNAVAILABLE status.

   By default, the gauges do not trigger the UNAVAILABLE status.

   As discussed in [Endpoint Average Response Time (Milliseconds) gauge](paz_endpoint_avg_resp.html) and [HTTP Processing (Percent) gauge](paz_http_proc_gauge.html), use the `dsconfig` command to adjust the following values for your environment. Each system is different so you might need to adjust the values several times to determine your ideal configuration.

   1. For the `Endpoint Average Response Time (Milliseconds)` gauge, set `critical-value`.

   2. For the `HTTP Processing (Percent)` gauge, set both `critical-value` and `server-unavailable-severity-level`.

3. Configure the container orchestrator to use the `available-or-degraded-state` endpoint to detect whether the server is alive.

   For information about the endpoint, see [Availability servlet](paz_server_status.html#availability_servlet).