Volcengine PostgreSQL
Volcengine PostgreSQL Metrics, including CPU usage, TPS, deadlocks, etc.
Configuration¶
Install Func¶
It is recommended to activate Guance Integration - Extensions - DataFlux Func (Automata): all prerequisites are automatically installed. Please proceed with script installation.
If deploying Func manually, refer to Manual Deployment of Func
Install Script¶
Note: Please prepare the required Volcengine AK in advance (for simplicity, you can grant global read-only permissions
ReadOnlyAccess).
To synchronize monitoring data of PostgreSQL cloud resources, we install the corresponding collection script: "Guance Integration (Volcengine-PostgreSQL Collection)" (ID: integration_volcengine_postgresql).
Click [Install], then enter the corresponding parameters: Volcengine AK, Volcengine account name.
Click [Deploy Startup Script], the system will automatically create the Startup script set and configure the corresponding startup script.
After enabling, you can see the corresponding automatic trigger configuration in "Manage / Automatic Trigger Configuration". Click [Execute] to immediately execute it once without waiting for the scheduled time. Wait a moment, you can view the execution task records and corresponding logs.
If you want to collect corresponding logs, you also need to enable the corresponding log collection script. If you want to collect bills, enable the cloud bill collection script.
Verification¶
- In "Manage / Automatic Trigger Configuration", confirm whether the corresponding task has the corresponding automatic trigger configuration, and you can also view the corresponding task records and logs to check for any anomalies.
- In Guance, "Infrastructure / Custom", check if asset information exists.
- In Guance, "Metrics", check if there is corresponding monitoring data.
Metrics¶
- Measurement
volcengine_vcm_rds_postgresql
| Metric Name | Metric Description | Unit |
|---|---|---|
replication_delay |
Master-slave replication delay | second |
db_conflicts |
Transaction conflicts per second | count/second |
replication_flush_lag |
Master-slave flush_lag | second |
replication_write_lag |
Master-slave write_lag | second |
unarchived_wal_segments_count |
Number of wal files to be archived | count |
active_connection |
Active connections | count |
idle_connection |
Idle connections | count |
idle_in_txn_connection |
Inactive transactions | count |
rows_inserted |
Rows inserted per second | count/second |
rows_updated |
Rows updated per second | count/second |
rows_deleted |
Rows deleted per second | count/second |
slow_queries |
Slow queries per second | count/second |
slow_queries_increment |
Number of slow queries in 30 seconds | count |
total_connection |
Total connections | count |
connection_used_util |
Connection usage rate | percent |
tps |
Transactions per second | count/second |
commits_per_second |
Commits per second | count/second |
rollbacks_per_second |
Rollbacks per second | count/second |
longest_transaction_exec_time |
Longest transaction execution time | second |
db_max_age_xids |
Database maximum age xids | none |
locks_ungranted_count |
Lock waits | count |
read_only_status |
Global read-only status | none |
shared_buffers_blks_hit |
Cache hits per second | count/second |
shared_buffers_blks_hit_rate |
Cache hit rate | percent |
locks_granted_count |
Lock holds | count |
error_queries |
Error queries per second | count/second |
error_queries_increment |
Error query increment in 30 seconds | count |
instantaneous_slow_queries |
Instantaneous slow queries | count |
dead_locks_count |
Database deadlocks | count |
prepared_xacts_count |
2pc transactions | count |
locks_ungranted_count_over_1h |
Lock waits over 1h | count |
db_fetched_returned_ratio |
Data return to scan ratio | percent |
qps |
Queries per second | count/second |
slow_queries_custom_increment |
Number of slow queries in n seconds | count |
oldest_prepared_xacts_duration |
Longest duration of 2pc transactions | second |
rows_fetched |
Rows fetched per second | count/second |
rows_returned |
Rows scanned per second | count/second |
transaction_success_rate |
Transaction success rate | percent |
proxy_connection |
Proxy connections | count |
proxy_qps |
Proxy qps | count/second |
proxy_cpu_util |
Proxy cpu usage rate | percent |
proxy_mem_util |
Proxy node memory usage rate | percent |
cpu_util |
CPU usage rate | percent |
mem_util |
Memory usage rate | percent |
disk_util |
Disk usage rate | percent |
user_cpu_util |
User CPU usage rate | percent |
sys_cpu_util |
System CPU usage rate | percent |
cache_mem_usage |
Cache memory usage | bytes(si) |
rss_mem_usage |
RSS memory usage | bytes(si) |
disk_usage |
Disk usage | bytes(si) |
log_disk_usage |
Log disk usage | bytes(si) |
wal_disk_usage |
WAL log disk usage | bytes(si) |
base_disk_usage |
Data file disk usage | bytes(si) |
temp_file_disk_usage |
Temporary file disk usage | bytes(si) |
network_receive_throughput |
Network input throughput | bytes/second(si) |
network_transmit_throughput |
Network output throughput | bytes/second(si) |
db_size |
Database size | bytes(si) |
db_expansion_rate |
Database expansion rate | bytes/second(si) |
slot_max_wal_accumulation |
Maximum wal accumulation of replication slot | bytes(si) |
inactive_slot_count |
Number of inactive replication slots | count |
slot_max_wal_accumulation_disk_ratio |
Maximum wal accumulation disk ratio of replication slot | percent |
db_max_table_size |
Maximum table size of database | bits(iec) |
Object¶
The collected Volcengine PostgreSQL object data structure can be seen in "Infrastructure - Custom".
{
"fields": {
"address_object": "xxxxxxxx",
"charge_detail": "xxxxxxxx",
"create_time": "2025-11-06T07:34:07.000Z",
"dbengine_version": "PostgreSQL_14",
"instance_status": "Running",
"message": "xxxxxxxx",
"node_spec": "rds.postgres.1c2g",
"storage_space": "20",
"storage_type": "LocalSSD",
"subnet_id": "subnet-3i6glfgpn5fr45r0lrqxxxxxxxx",
"vpc_id": "vpc-3qdy52316jny87prmlxxxxxxxx"
},
"measurement": "volcengine_postgresql",
"tags": {
"account_name": "pdsa-dev",
"cloud_provider": "volcengine",
"instance_id": "postgres-588f06xxxxxxxx",
"instance_name": "fyb-dev",
"instance_type": "HA",
"name": "postgres-588f06xxxxxxxx5",
"project_name": "default",
"region_id": "cn-shanghai",
"zone_id": "cn-shanghai-a"
}
}
]