Monitoring of PostgreSQL cluster, nodes, and databases for 1C

Last update: July 10 2026

In managed PostgreSQL databases for 1C, you can monitor the cluster status.

To evaluate the overall cluster status, check its status.

For more detailed analysis, some metrics can be viewed as charts in the control panel:

• cluster node metrics;
• database metrics;
• connection pooler metrics.

A full set of available metrics can be exported in Prometheus format.

When analyzing graphs, keep in mind that the time in the Control Panel corresponds to the time on your device and does not depend on the region where the cluster is located.

note

For example, you created a cluster in Tashkent, in the uz-1 pool. The device you used to log into the control panel is set to the Moscow time zone. The time on the metrics charts will be displayed in the Moscow time zone.

View cluster status

1. In the control panel, on the top menu, click Products and select Managed Databases.
2. Open the Active tab.
3. Check the cluster status in the cluster row.

ACTIVE	Cluster is active
CREATING	Cluster is being created
UPDATING	Cluster is updating
RESIZING	Cluster is scaling
ERROR	An error occurred, create a ticket
DISK FULL	The disk is full; the cluster is in read-only mode. To allow read and write operations, clean up the disk or scale the cluster and choose a configuration with a larger disk size
DEGRADED	Some cluster nodes are unavailable
DELETING	Cluster is being deleted

View cluster node status

1. In the control panel, on the top menu, click Products and select Managed Databases.
2. Open the Active tab.
3. Open the cluster page → Monitoring tab.
4. In the Cluster monitoring block, click Cluster nodes.
5. Select the nodes for which you want to view metrics.
6. View available cluster node metrics.

Cluster node metrics in the control panel

Memory	Occupied memory excluding operating system cache and buffers, in percent or gigabytes
vCPU	Percentage of cluster node cores load
CPU iowait	Percentage of time the processor spent waiting for input/output
Volume	Occupied disk space in percent or gigabytes. It accounts for the part of disk space reserved for service requirements that is unavailable for database storage. For more information on reserving disk space, see the guide Using disk space in a PostgreSQL cluster for 1C
Load Average	The average system load over a period of time. It shows how many processes are being handled by the cluster cores. The indicator is presented as three values—for one minute, five minutes, and 15 minutes. These values should not exceed the number of cores on the node
OOM	Number of processes that ended with an Out of Memory error due to RAM shortage
Disk load	Read and write data speed in KB/s or number of read and write operations per second
Network load	Number of bits or packets sent and received via the network interface

View database status

1. In the control panel, on the top menu, click Products and select Managed Databases.
2. Open the Active tab.
3. Open the cluster page → Monitoring tab.
4. In the Cluster monitoring block, click Databases.
5. Select the nodes for which you want to view metrics.
6. View available database metrics.

Database metrics in the control panel

Statistics file size	Total size of the statistics file in kilobytes
Cache hit	Percentage of data in the request read from the cache — the ratio of blks_hit to the sum of blks_hit and blks_read
Row operations	Number of rows affected by operations in the selected database per second: tup_deleted — number of rows deleted by operations per second; ; tup_fetched — number of rows retrieved by operations per second; ; tup_inserted — number of rows inserted by operations per second; ; tup_returned — number of rows returned by operations per second; ; tup_updated — number of rows updated by operations per second
Locks	Number of locks in each cluster database
Deadlocks	Number of deadlocks in each database
Transactions	Number of transactions per second in each cluster database
Connections	Number of connections to each cluster database and total number of connections to all databases
Temporary file size	Total size of temporary files in kilobytes
WAL file size	Total size of WAL files in megabytes
Duration of the longest request	Duration of the longest request in each cluster database for a time period
Database size	Total size of the selected database in megabytes

View connection pooler status

1. In the control panel, on the top menu, click Products and select Managed Databases.
2. Open the Active tab.
3. Open the cluster page → Monitoring tab.
4. In the Cluster monitoring block, click Connection pooler.
5. Select the nodes for which you want to view metrics.
6. View available connection pooler metrics.

Connection pooler metrics in the control panel

Maximum client wait time in queue	Maximum client wait time in queue in the selected database in seconds
Response wait time from server	Wait time for a response from the node in the selected database in seconds
Active connections to the server	Number of server connections associated with clients, in the selected database
Client connections to the pool	Number of client connections to the pool in the selected database: pools_client_active_connections — number of client connections associated with server connections or idle without requests; ; pools_client_waiting_connections — number of client connections where the request has been sent, but there is no connection to the node yet

Export metrics in Prometheus format

Historical information is not available for clusters; metrics are requested only in real time. A list of all metrics supported in managed databases and their descriptions can be viewed in the Metrics in Prometheus format table.

1. Get a token.
2. Get metrics in Prometheus format.

1. Get a token

The token provides access to metrics for all project clusters in one pool.

1. In the control panel, on the top menu, click Products and select Managed Databases.

2. Open the Active tab.

3. Open the cluster page → Monitoring tab.

4. In the Prometheus tokens block, click Create token. The token will be generated automatically.

5. Copy the token. To do this, click in the token line.

2. Get metrics in Prometheus format

Configuration file

1. Add to the Prometheus configuration file:

   scrape_configs:
     - job_name: get-metrics-from-dbaas
       scrape_interval: 1m
       static_configs:
         - targets:
           - '<domain>'
       scheme: https
       authorization:
         type: Bearer
         credentials: <token>

   Specify:

   • <domain> is the Managed Databases API domain. It is part of the URL used to access the API without https:// and /v1, for example, ru-3.dbaas.selcloud.ru. The URL depends on the region and pool and can be found in the list of URLs;
   • <token> — the token you copied when getting the token in step 5.

2. Open the page in your browser where metrics in Prometheus format will be available:

   http://<ip_address>:9090/targets

   Specify <ip_address> — the IP address where Prometheus is installed.

3. Set up monitoring and alerts for database clusters yourself.

CLI

1. Open the CLI.

2. To get metrics, send a request:

   curl -L "https://<domain>/metrics" -H "Authorization: Bearer <token>"

   Specify:

   • <domain> is the Managed Databases API domain. It is part of the URL used to access the API without https:// and /v1, for example, ru-3.dbaas.selcloud.ru. The URL depends on the region and pool and can be found in the list of URLs;
   • <token> — the token you copied when getting the token in step 5.

   Available metrics in Prometheus format will appear in the response.

3. Set up monitoring and alerts for database clusters yourself.

Metrics in Prometheus format

Metrics in Prometheus format are provided for all clusters. A specific cluster can be found by its database cluster ID in the ds_id label.

Infrastructure level metrics

dbaas_memory_percent	Occupied memory excluding operating system cache and buffers (RAM) in percent
dbaas_memory_bytes	Occupied memory excluding operating system cache and buffers (RAM) in bytes
dbaas_oom_count	Number of processes that ended with an Out of Memory error due to RAM shortage
dbaas_cpu	vCPU usage on database cluster nodes in percent
dbaas_cpu_iowait	Input/output wait time in percent
dbaas_disk_percent	Occupied disk space in percent. It accounts for the part of disk space reserved for service requirements that is unavailable for database storage. For more information on reserving disk space, see the guide Using disk space in a PostgreSQL cluster for 1C
dbaas_disk_bytes	Occupied disk space in bytes. It accounts for the part of disk space reserved for service requirements that is unavailable for database storage. For more information on reserving disk space, see the guide Using disk space in a PostgreSQL cluster for 1C
dbaas_disk_read_iops	Number of read operations per second
dbaas_disk_write_iops	Number of write operations per second
dbaas_disk_read_bytes	Disk read speed in bytes per second
dbaas_disk_write_bytes	Disk write speed in bytes per second
dbaas_node_load1	Average system load over one minute. Shows how many processes are being handled by cluster cores
dbaas_node_load5	Average system load over five minutes. Shows how many processes are being handled by cluster cores
dbaas_node_load15	Average system load over 15 minutes. Shows how many processes are being handled by cluster cores
dbaas_network_receive_bytes	Number of bytes received via the network interface
dbaas_network_transmit_bytes	Number of bytes sent via the network interface
dbaas_network_receive_packets	Number of packets received via the network interface per second
dbaas_network_transmit_packets	Number of packets sent via the network interface per second
dbaas_role	Node role: 0 — role is unknown; ; 1 — master; ; 2 — replica

Application level metrics

dbaas_connections	Number of active connections to the PostgreSQL process For example, you can use the labels: ds_name — database cluster name; ; datname — database name.
dbaas_total_connections	Total number of established connections to the PostgreSQL process
dbaas_max_tx_duration	Duration of the longest request in seconds
dbaas_xact_commit_rollback	Number of transactions per second in each cluster database. For example, you can use the labels: ds_name — database cluster name; ; datname — database name.
dbaas_tup_deleted	Number of rows per second deleted by queries in the database
dbaas_tup_fetched	Number of rows per second retrieved by queries in the database
dbaas_tup_inserted	Number of rows per second inserted by queries in the database
dbaas_tup_returned	Number of rows per second returned by queries in the database
dbaas_tup_updated	Number of rows per second modified by queries in the database
dbaas_xact_commit	Number of committed transactions per second in the database
dbaas_xact_rollback	Number of transactions per second in the database for which a rollback was performed
dbaas_cache_hit_ratio	Percentage of data in the request read from the cache — the ratio of blks_hit to the sum of blks_hit and blks_read
dbaas_deadlocks	Number of deadlocks per second in each database. For example, you can use the labels: ds_name — database cluster name; ; datname — database name.
dbaas_locks	The number of locks per second in each cluster database. For example, you can use labels: ds_name — database cluster name; ; datname — database name.
dbaas_pg_pgss_query_texts_size_bytes	Size of the statistics file from pg_stat_statements in bytes
dbaas_pg_total_wals_size_bytes	Size of the directory with WAL files in bytes
dbaas_pg_tmp_size_bytes	Size of PostgreSQL temporary files in bytes
dbaas_databases_size_bytes	Total database size in bytes. For example, you can use the datname label — database name
dbaas_pg_trx_max_age	Number of transactions performed after the last freeze using the VACUUM FREEZE or AUTOVACUUM operation
dbaas_pg_trx_percent_before_vacuum_freeze	Shows how much the age of the earliest transaction in the database has approached the threshold after which PostgreSQL forces a VACUUM FREEZE operation. The threshold is determined by the autovacuum\_freeze\_max\_age parameter
dbaas_pg_trx_percent_before_wraparound_risk	Shows how much the age of the earliest transaction in the database has approached the threshold after which a transaction ID wraparound is possible (wraparound)