Yandex MPP Analytics for PostgreSQL cluster and host state monitoring
Data on the cluster and host state is available in the management console
Diagnostic information about cluster states is presented as graphs.
Charts are updated every 15 seconds.
Note
The most appropriate multiple units (MB, GB, and more) are automatically used in charts.
Monitoring principles
To streamline troubleshooting, the management console provides dashboards for visual diagnostics, built upon the following principles:
- Hierarchy: Diagnostics follow a top-down approach. You start with aggregate cluster health signals and, if issues are observed, you can drill down into individual components (e.g., a cluster, pooler, or hybrid storage) or consumed resources.
- Efficiency: Instead of dozens of charts, you are only exposed to key indicators with a focus on signals, i.e., metrics with clear thresholds that help instantly spot an issue.
- Autonomy: Documents and dashboards are designed to help you independently identify the root-cause of degradation without requesting assistance from support.
- Continuous iteration: Diagnostic tools are developed step-by-step based on actual user experience. We continuously analyze requests for improvements to deliver more accurate and streamlined diagnostics.
Signaling system
The top of the dashboard displays signals that aggregate the state of multiple metrics. They use a traffic-light color-coding system:
| Stage | Value | Description |
|---|---|---|
| 🟢 OK | 2 |
All critical indicators are healthy. The cluster and its components are operating normally. |
| 🟠 Warn | 1 |
Minor deviations are detected. The cluster is functional but requires attention to prevent performance degradation (e.g., connection queue growth or increased latency). |
| 🔴 Crit | 0 |
Critical degradation. The cluster is unstable, components are unavailable, or resources are exhausted. Immediate remediation is required. |
| ⚪ Unknown | -1 |
Data is missing or the status is undefined. |
Cluster dashboard
The primary diagnostic tool is the Cluster dashboard, which serves as a single pane of glass for cluster state management.
-
Open the folder dashboard
. -
Navigate to Yandex MPP Analytics for PostgreSQL.
-
Click the name of your cluster and select the
Monitoring tab.This opens a page displaying a dashboard with your Yandex MPP Analytics for PostgreSQL cluster charts and signals.
-
To get started with Yandex Monitoring metrics, dashboards, or alerts, click Open in Monium in the top panel.
The dashboard consists of the following sections:
-
Signals:
- Cluster: General cluster status.
- Pooler: Connection pooler status.
- Connections: Connection status.
- Resources: Status of host resources.
- Queries: Read/write test query status.
-
Cluster:
- Read availability: Cluster read availability over the last five minutes.
- Write availability: Cluster write availability over the last five minutes.
- Master switch history: Master failover history (current master FQDN).
- XID utilization: Transaction counter
utilization percentage. - Segments down: Number of segments currently in the
downstate. - Segments not in preferred role: Number of segments that are not in their preferred role.
- Segments not synchronised: Number of unsynchronized segments.
- Log events: Number of
WARNING,ERROR, andFATALevents in logs.
-
Pooler:
- Availability: Pooler availability over the last five minutes.
- CPU usage: CPU utilization by the pooler process.
- Memory usage: Memory utilization by the pooler process.
- Network usage: Amount of sent and received data.
- Server connections: Active and available server connections.
- Client connections: Active client connections.
- Query timings: Distribution of query durations by percentiles.
-
Connections:
- Total master connections utilization: Total utilization of master connections.
- Idle in transaction master connections utilization: Utilization of connections that are idle in transaction.
- Master connections: Detailed master node connection breakdown by state:
active,idle,idle in transaction,waiting,aborted,total(total number for all states), andmax(limit). - Total segments connections utilization: Connection utilization by segments.
-
Resources:
- This section is split into the Master hosts and Segment hosts subgroups.
- Load Average: Average load over 15 minutes.
- CPU utilization: CPU utilization.
- Virtual memory consumption: Total virtual memory used.
- Physical memory consumption: Total physical memory used.
- Network packets: Network packets sent and received per second.
- Network packets in queues: Number of packets in network interface queues.
- Network traffic: Amount of outgoing and incoming traffic.
- Disk space utilization: Percentage of used disk space.
- Disk IO: Disk read and write throughput in bytes per second.
- Interconnect retransmits ratio (segments only): Ratio of resent Interconnect packets to total sent packets.
-
Queries:
- Read test query duration: Test read query duration.
- Write test query duration: Test write query duration.
- Read duration from each segment: Test read query duration by segments.
- Queries sent to the cluster: Number of new and failed queries.
- Queries execution time distribution: Histogram of historical query durations.
- Running queries execution time distribution: Distribution histogram of active query durations.
- Spill files count: Total and per-host count of temporary files.
- Spill files size: Total and per-host size of temporary files.
-
Resource groups:
- Charts in this section display information by process groups:
- admin_group: Administrative group.
- default_group: Default group.
- Connections utilization by resource group: Connection utilization.
- CPU usage by resource group: CPU utilization.
- Memory utilization by resource group: Memory utilization percentage.
- Memory usage by resource group: Absolute value of used and available memory.
- Running transactions by resource group: Number of running transactions.
- Executed transactions by resource group: Transaction frequency.
- Queueing transactions by resource group: Number of transactions in the queue.
- Charts in this section display information by process groups:
-
Background activities:
- Vacuum: catalog:
- Catalog size: System catalog size per database.
- Catalog percent of dead tuples: Percentage of dead tuples within the catalog per database.
- Vacuum: pg_attribute:
- pg_attribute size: Size of the
pg_attributetable per database. - pg_attribute percent of dead tuples: Percentage of dead tuples in the
pg_attributetable per database.
- pg_attribute size: Size of the
- Vacuum/analyze: user tables:
- Tables vacuum age: Distribution of tables by number of days since the last vacuuming (
VACUUM). - Tables analyze age: Distribution of tables by number of days since the last statistics collection (
ANALYZE).
- Tables vacuum age: Distribution of tables by number of days since the last vacuuming (
- Vacuum: catalog:
-
Hybrid storage:
- CPU usage per host: CPU utilization by
yproxyper cluster host. - Memory usage per host: Memory utilization by
yproxyper cluster host. - Storage requests: Number of storage requests (total, successful, and failed).
- Storage objects count: Total number of objects in storage.
- Storage objects size: Total size of objects in storage.
- CPU usage per host: CPU utilization by
Hosts dashboard
To view detailed information on the state of individual Yandex MPP Analytics for PostgreSQL hosts, refer to the Hosts dashboard. At the top of the dashboard, there are resource status signals (CPU, Memory, Disk), while below, detailed charts by category.
-
Open the folder dashboard
. -
Navigate to Yandex MPP Analytics for PostgreSQL.
-
Click the cluster name and select the
Monitoring → Hosts tab. -
Select the host you need.
The page that opens will display state charts for the cluster host.
-
To get started with Yandex Monitoring metrics, dashboards, or alerts, click Open in Monium in the top panel.
The dashboard consists of the following sections:
-
Signals:
- CPU: Processor load.
- Memory: Virtual memory usage and availability.
- Disk: Used data disk space.
-
CPU:
- Load average 15 min: 15-minute average CPU load.
- Load average 5 min: Five-minute average CPU load.
- Load average 1 min: One-minute average CPU load.
- CPU utilization: Percentage of CPU core utilization.
- CPU pressure time: Time in microseconds during which processes were waiting for CPU access.
- CPU: CPU time breakdown across states (
user,system,idle,iowait, and so on). - Process statuses: Number of processes in various states:
running,idle,interruptible sleep,uninterruptible sleep, andzombie.
-
Memory:
- Virtual memory utilization: Percentage of virtual memory used.
- Virtual memory usage: Amount of virtual memory used, in bytes.
- Out of memory count: Number of out-of-memory events.
- Memory utilization: Percentage of physical RAM used.
- Memory usage: Amount of physical memory used, in bytes.
- Memory pressure time: Time during which processes were waiting for memory access.
-
Disk:
- Disk usage percent: Percentage of data disk space used.
- Disk usage: Amount of data stored on disk, in bytes.
- Disk read/write operations: Number of read and write operations per second.
- Disk read/write bytes: Volume of data read from and written to disk per second, in bytes.
- Disk read and write time: Average time to complete read and write operations.
-
Disk Metrics Details:
- Disk read latency (percentiles): Disk read operation latencies, percentiles.
- Disk write latency (percentiles): Disk write operation latencies, percentiles.
- Disk read throttler latency (percentiles): Throttler-introduced disk read operation delay, percentiles.
- Disk write throttler latency (percentiles): Throttler-introduced disk write operation delay, percentiles.
- Disk read operations: Average and maximum number of disk read operations per second.
- Disk write operations: Average and maximum number of disk write operations per second.
- Disk used quota: Percentage of disk operation quota usage.
- Disk read bytes: Average and maximum number of bytes read from disk.
- Disk write bytes: Average and maximum number of bytes written to disk.
-
Network:
- Client network reliability: Network interface reliability indicator.
- Client network packets sent: Number of packets sent on the interface per second.
- Client network packets received: Number of packets received on the interface per second.
- Client network errors: Number of errors sending and receiving packets.
- Client network drops: Number of dropped packets.
- Client network interface errors/drops: Detailed breakdown of errors and drops per interface.
- Client network bytes: Network traffic volume on the interface, in bytes per second.
PXF monitoring
To view detailed information about the PXF state:
-
Open the folder dashboard
. -
Navigate to Yandex MPP Analytics for PostgreSQL.
-
Click the cluster name and select the
Monitoring → PXF tab.The page that opens will display PXF state charts.
-
To get started with Yandex Monitoring metrics, dashboards, or alerts, click Open in Monium in the top panel.
The page displays the following charts:
- Liveness: PXF state on hosts.
- JVM memory: JVM PXF memory usage, in GB.
- JVM threads: Number of JVM PXF threads.
- Connections: Number of connections.
- PXF threads: Number of PXF threads.
- PXF Busy threads: Number of busy PXF threads.
- Log messages: Number of messages of the
warn,trace,info,fatal,error, anddebugtypes. - Sent data: Amount of sent data.
- Received data: Amount of received data.
- File handles: Number of files opened during the PXF process.
- Sent records: Number of records sent by PXF.
- Received records: Number of records received by PXF.
Monitoring resource groups
To view information on Yandex MPP Analytics for PostgreSQL resource groups:
-
Open the folder dashboard
. -
Navigate to Yandex MPP Analytics for PostgreSQL.
-
Click the cluster name and select
Monitoring → Resource groups.The page that opens will display performance charts for resource groups.
-
To get started with Yandex Monitoring metrics, dashboards, or alerts, click Open in Monium in the top panel.
The page displays the following charts:
- CPU Usage: Total CPU usage across all hosts in a resource group.
- Memory Usage: Total memory usage across all hosts in a resource group.
- Running queries: Current number of active transactions in a resource group.
- Queueing queries: Current number of queueing transactions for this resource group.
- Executed queries: Total number of transactions executed in a resource group since the most recent cluster startup (excluding Running queries).
- Queued queries: Total number of transactions enqueued for this resource group since the most recent cluster startup (excluding Queueing queries).
You can also view information on resource groups for each Yandex MPP Analytics for PostgreSQL cluster host:
-
Open the folder dashboard
. -
Navigate to Yandex MPP Analytics for PostgreSQL.
-
Click the cluster name and select
Monitoring → Resource groups per host.The page that opens will display performance charts for resource groups by host.
-
To get started with Yandex Monitoring metrics, dashboards, or alerts, click Open in Monium in the top panel.
The page displays the following charts:
- CPU Usage: Total CPU usage in a resource group within a host.
- Memory Usage: Total memory usage in a resource group within a host.
Integration with Yandex Monitoring
To configure state indicator alerts for a cluster and hosts:
- In the management console
, select the folder with the cluster for which you want to set up alerts. - Navigate to
Monitoring. - Under Service dashboards, select:
- Yandex MPP Analytics for PostgreSQL — Cluster Overview to configure cluster alerts.
- Yandex MPP Analytics for PostgreSQL — Host Overview to configure host alerts.
- In the indicator chart, click
and select Create alert. - If the chart shows multiple metrics, select the data query to generate the metric and click Continue. For more on the query language, see this Yandex Monitoring guide.
- Set the
AlarmandWarningthresholds for notifications. - Click Create alert.
- For signals, we recommend configuring alerts for when the status switches to
Crit(0) orWarn(1).
To have other cluster health indicators monitored automatically:
- Create an alert.
- Add a status metric.
- In the alert parameters, set the alert thresholds.
For a complete list of supported metrics, see this Monitoring guide.
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 the health state and status of a cluster:
- Open the folder dashboard
. - Navigate to Yandex MPP Analytics for PostgreSQL.
- 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:
|
| DEAD | The cluster is down: none of its hosts are running. | Make a support request
|
| UNKNOWN | Cluster state is unknown. | Make a support request
|
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 |
| STATUS_UNKNOWN | The cluster is unable to determine its status | If the cluster remains in this status for a long time, contact support |
Greenplum® and Greenplum Database® are registered trademarks or trademarks of Broadcom Inc. in the United States and/or other countries.