PostgreSQL on Amazon RDS metrics and alerts
Published 28 March 2024
If you can't find a specific metric or alert you would like to use when monitoring your RDS instances, send us feedback.
Metrics
Machine metrics
To get access to machine metrics in Amazon RDS you need to provide Redgate Monitor with your AWS API credentials.
The following table summarizes the machine metrics that Redgate Monitor can collect, for Amazon RDS servers, and which of those are collected only if Amazon RDS Enhanced Monitoring is enabled for your Amazon RDS instances:
| Metric name | Amazon RDS Enhanced Monitoring required? |
|---|---|
| Machine: Processor time | - |
| Machine: Memory used | Yes |
| Network utilization | - |
| Disk used | Yes |
| Disk capacity | Yes |
| Disk read and write bytes/sec | - |
| Disk transfers/sec | - |
This documentation contains a list of metrics and alerts that are available when monitoring PostgreSQL on RDS instances. Send us feedback if there are additional metrics or alerts you'd find valuable.
Metrics
The following lists the metrics Redgate Monitor collects and exposes on the Analysis page:
PostgreSQL on RDS metrics -
Available at the instance level as an aggregate, and at the individual database level:
- Number of connections
- Transactions committed / rolled back
- Query overflow to temp data bytes sec
- Block write time
- Block read time
- Transactions committed / second
- Transactions rolled back / second
- Deadlocks / sec
- Cache hit ratio
Alerts
The following is a list of alerts available for PostgreSQL on RDS:
- PostgreSQL specific alerts
- Configuration change
- Database unavailable
- Internal Redgate Monitor error (PostgreSQL)
- Long-running query
- Long-running transaction
- Long-running idle transaction
- Monitoring error (data collection)
- Monitoring stopped (credentials)
- Instance unreachable
- Low cache hit ratio
- Host machine alerts
- Disk average read time
- Disk average write time
- Disk space
- Internal Redgate Monitor error (host)
- Machine unreachable
- Monitoring error (host machine data collection)
- Monitoring stopped (host machine credentials)
- Physical memory
- Processor under-utilization
- Processor utilization
Alerts
Alerts are based on metrics, so if the metric, or metrics, used by an alert require AWS API credentials or RDS Enhanced Monitoring to be collected, the alert will consequently have the same requirements.
The following table describes the requirements for the supported alerts:
| Alert name | Level raised | AWS API required? | Amazon RDS Enhanced Monitoring required? |
|---|---|---|---|
Configuration change | PostgreSQL | - | - |
Database unavailable | PostgreSQL | - | - |
| Disk space | Machine | yes | yes |
| Internal Redgate Monitor error (host) | Machine | yes | |
Internal Redgate Monitor error (instance) | PostgreSQL | - | - |
Instance unreachable | PostgreSQL | - | - |
Long-running query | PostgreSQL | - | - |
Long-running transaction | PostgreSQL | - | - |
Long-running idle transaction | PostgreSQL | - | - |
Low cache hit ratio | PostgreSQL | - | - |
| Monitoring error (host data collection) | Machine | yes | - |
| Monitoring error (host credentials) | Machine | yes | - |
Monitoring error (instance data collection) | PostgreSQL | - | - |
Monitoring stopped (instance credentials) | PostgreSQL | - | - |
Physical memory | Machine | yes | yes |
| Processor utilization | Machine | yes | - |
| Processor under-utilization | Machine | yes | - |
