Contact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.

Sharded PostgreSQL cluster and host state monitoring

Written by
Updated at May 14, 2026

Data on the cluster and host state is available in the management console. You can view them on the Monitoring tab of the cluster management page or in Yandex Monitoring.

Diagnostic information about cluster states is presented as graphs.

Chart update rate:

  • Standard hosts and hosts with an increased RAM to vCPU ratio (memory-optimized): 15 seconds.
  • Hosts with a guaranteed vCPU share under 100% (burstable): 150 seconds.

Note

The most appropriate multiple units (MB, GB, and more) are automatically used in charts.

You can configure alerts in Yandex Monitoring to receive notifications about cluster failures. In Yandex Monitoring, there are two alert thresholds: Warning and Alarm. If the specified threshold is exceeded, you will receive alerts via the configured notification channels.

Cluster health state monitoring

To view health details for a Managed Service for Sharded PostgreSQL cluster:

  1. Navigate to Yandex Managed Service for Sharded PostgreSQL.

  2. Click the cluster name and open the Monitoring tab.

  3. To get started with Yandex Monitoring metrics, dashboards, or alerts, click Open in Monium in the top panel.

You will see the following charts:

  • Under Cluster:

    • SPQR is Alive, [boolean]: Health status of router hosts.
    • ETCD is Alive, [boolean]: Health status of coordinator hosts.
    • Maximum CPU usage: Peak processor core load.
    • Average CPU usage: Average processor core workload.
    • Maximum memory usage: Peak RAM usage (in bytes). At high loads, the value of the Free space metric decreases, while the others increase.

  • Sessions → Sessions count: Number of active client connections to the router.

  • Connections → Backend connections count: Number of active connections from the router to shard hosts.

  • Under Network:

    • Packets received/sent: Network packet exchange rate, in packets per second.
    • Network received/sent bytes: Total amount of received and sent data, in bytes.

  • Under Time quantiles:

    • Router time quantiles, ms: Execution time of client requests to each router at the quantiles set by the Time Quantiles configuration.
    • Shard time quantiles, ms: Execution time of requests from the router to shard hosts at the quantiles set by the Time Quantiles configuration.

Host state monitoring

To view detailed information about the status of individual Managed Service for Sharded PostgreSQL hosts:

  1. Navigate to Yandex Managed Service for Sharded PostgreSQL.
  2. Click the cluster name and open the Monitoring → Hosts tab.
  3. Click the line of the host in the list.

This page displays workload charts for an individual cluster host:

  • CPU usage: Processor core workload. With increased workload, the Idle value drops.
  • Memory usage: Use of RAM, in bytes. At high loads, the value of the Free space metric decreases, while the others increase.
  • Packets received/sent: Network packet exchange rate, in packets per second.
  • Network received/sent bytes: Total amount of received and sent data, in bytes.
  • Under Time quantiles:
    • Router time quantiles, ms: Execution time of client requests to router at the quantiles set by the Time Quantiles configuration.
    • Shard time quantiles, ms: Execution time of requests from the router to shard hosts at the quantiles set by the Time Quantiles configuration.

Setting up alerts in Yandex Monitoring

To configure automatic monitoring of key cluster health metrics:

  1. In the management console, select the folder with the cluster for which you want to set up alerts.
  2. Go to Monitoring.
  3. Under Service dashboards, select:
    • Managed Service for Sharded PostgreSQL — Cluster Overview to configure cluster alerts.
    • Managed Service for Sharded PostgreSQL — Host Overview to set up host alerts.
  4. In the chart you need, click and select Create alert.
  5. If the chart shows multiple metrics, select the data query to generate a metric and click Continue. You can learn more about the query language in the Yandex Monitoring guides.
  6. Set the Alarm and Warning thresholds to trigger the alert.
  7. Click Create alert.

To have other cluster health indicators monitored automatically:

  1. Create an alert.
  2. Add a status metric.
  3. In the alert parameters, set the alert thresholds.

Recommended threshold values for selected metrics:

Metric Designation Alarm Warning
Number of healthy router hosts spqr-is-alive <number_of_router_hosts> - 2 <number_of_router_hosts> - 1
Number of healthy coordinator hosts etcd-is-alive <number_of_coordinator_hosts> - 2 <number_of_coordinator_hosts> - 1

Cluster health and status

The State of a cluster shows the health of its hosts, while the Status shows whether the cluster is started, stopped, or is at an intermediate stage.

To view cluster health and status:

  1. Navigate to the folder dashboard and select Yandex Managed Service for Sharded PostgreSQL.
  2. In the cluster row, hover over the indicator in the Availability column.

Cluster health states

State Description Suggested actions
ALIVE Cluster is operating normally. No action is required.
DEGRADED Cluster is not running at its full capacity: the state of at least one of the hosts is other than ALIVE. Run the diagnostics:
  • Go to the Hosts tab and see which hosts are not working.
  • Go to the Operations tab and make sure all operations are completed.
  • Make sure the cluster is not under maintenance.
If you cannot find the cause yourself, contact support.
DEAD The cluster is down: none of its hosts are running. Make a support request stating the following:
  • Cluster ID.
  • IDs of the last operations performed on it.
  • Time the cluster entered the DEAD state according to the availability charts.
UNKNOWN Cluster state is unknown. Make a support request stating the following:
  • Cluster ID.
  • IDs of the last operations performed on it.
  • Time the cluster entered the UNKNOWN state according to the availability charts.

Cluster statuses

Status Description Suggested actions
CREATING Preparing for the first start Wait a while and get started. The time it takes to create a cluster depends on the host class.
RUNNING The cluster is operating normally No action is required.
STOPPING The cluster is stopping After a while, the cluster status will switch to STOPPED and the cluster will be disabled. No action is required.
STOPPED The cluster is stopped Start the cluster to get it running again.
STARTING Starting the cluster that was stopped earlier After a while, the cluster status will switch to RUNNING. Wait a while and get started.
UPDATING Updating the cluster's configuration Once the update is complete, the cluster will get the status it had prior to the update: RUNNING or STOPPED.
ERROR Error when performing an operation with the cluster or during a maintenance window If the cluster remains in this status for a long time, contact support. You can see whether a cluster is available by its status.
STATUS_UNKNOWN The cluster is unable to determine its status If the cluster remains in this status for a long time, contact support.
Previous
Viewing cluster logs
Next
Deleting a cluster