Which privileges are required?

As the RDS root user: GRANT pg_monitor TO clustereye, plus CONNECT on each monitored database. All of it is read-only.

How is the platform detected?

Huawei Cloud RDS leaves no verifiable SQL marker — no marker role, GUC namespace or marker database. So ClusterEye does not guess: the platform comes from the provider you select at registration. That prevents a vanilla PostgreSQL server from being misclassified as Huawei.

← All databases

HW

Huawei Cloud RDS for PostgreSQL monitoring

Huawei Cloud RDS for PostgreSQL is monitored agentlessly in ClusterEye: the connection is made from the ClusterEye API server over a TLS session verified against Huawei's CA certificate, and nothing is installed on the RDS instance. In-database catalog views are combined with host metrics from Cloud Eye to show where the bottleneck is in an environment where the host is out of reach.

AgentlessDefault port: 5432Versions: RDS

What we read

pg_stat_activity — sessions, wait events and blocking chains

pg_stat_statements — per-query timing and call statistics (once enabled through the parameter group)

pg_stat_user_tables / user_indexes — dead tuple accumulation, vacuum history and index usage

pg_stat_replication — replication lag and replica state

transaction ID age — distance to wraparound and whether autovacuum is keeping up

database and table sizes — storage consumption and the growth curve

Cloud Eye — CPU, memory, disk and network metrics, via the node the instance publishes under

What it does specifically for Huawei Cloud RDS

Unified view with Cloud Eye host metrics

The in-database wait profile and the Cloud Eye host series share a timeline, separating a resource ceiling from a workload-driven slowdown.

TLS verified against the vendor CA

Huawei RDS presents a certificate signed by a CA that is not in the operating system trust store. ClusterEye takes that CA at registration and verifies the chain against it — connecting without turning certificate verification off.

Storage growth forecasting

Storage consumption is tracked and the date of reaching the limit projected.

Autovacuum and wraparound tracking

Dead tuple ratio, whether autovacuum is keeping up, and distance to transaction ID wraparound are tracked to give early warning.

Minimum privileges required

The baseline is read-only and safe to grant in production.

sql

-- Run as the RDS root user
CREATE ROLE clustereye LOGIN PASSWORD '<strong-password>';
GRANT pg_monitor TO clustereye;

-- repeat for every monitored database
GRANT CONNECT ON DATABASE <db> TO clustereye;

Prerequisites

·Agentless: the connection is made from the ClusterEye API server; nothing is installed on the RDS instance.

·TLS defaults to verify-ca — Huawei's CA is not in the operating system trust store, so you upload that certificate during registration.

·For query intelligence: enable pg_stat_statements through the parameter group, then run CREATE EXTENSION in each database.

·Host metrics (CPU, memory, disk) come from Cloud Eye and need an access key/secret and the project region. Without them in-database monitoring is unaffected; only the host series stays empty.

Install and privilege details →

Frequently asked questions

Nothing. The connection is made from the ClusterEye API server over 5432/tcp. The one piece of preparation is uploading Huawei's CA certificate at registration — it is needed because that CA is not in the operating system trust store, and it is preferable to disabling verification.

Start monitoring your Huawei RDS PostgreSQL estate in five minutes.

One command to install. Talk to us if you have questions.

Book a live demo Install and privilege details