AWS Builder Center is the official home for builders on AWS. Share and read what others are working on, follow people who inspire you, explore training and workshops, and find tools to support what you're building.
PostgreSQL RDS Performance Insights Not Showing Calls/Sec , Rows/Sec and Avg Latency
We are able to retrieve records from pg_stat_statements for Calls/Sec, Rows/Sec, and Avg Latency. However, nothing is visible at the console level. All configurations are properly set. We were able to see these records a month ago.
- Newest
- Most votes
- Most comments
The issue you're experiencing with PostgreSQL RDS Performance Insights not showing Calls/Sec, Rows/Sec, and Avg Latency metrics is not uncommon and can occur for several reasons.
First, ensure that Performance Insights is still enabled for your RDS cluster. Sometimes, these metrics may disappear if there have been changes to the configuration.
It's important to note that for RDS PostgreSQL, Performance Insights collects SQL statistics only at the digest level, not at the statement level. This means that the statistics are aggregated for similar queries rather than individual statements.
The fact that you can retrieve records from pg_stat_statements but can't see them in the console suggests that there might be an issue with how Performance Insights is collecting or displaying the data. This could be due to a few factors:
-
It's possible that the Performance Insights service needs some time to gather and process new data, especially if there have been recent changes or updates to your RDS instance.
-
There might be an issue with the performance_schema, which is crucial for collecting these metrics. Even if you haven't changed any default values, sometimes system updates or maintenance can affect these settings.
-
The instance type and storage configuration of your RDS instance should support the metrics you're trying to view. Make sure there haven't been any recent changes that might affect this.
-
In some cases, disabling and then re-enabling Performance Insights at the cluster level has resolved similar issues. After doing this, you might also want to reboot the instances to ensure the changes take effect.
-
For queries longer than 1,024 bytes, you may need to increase the track_activity_query_size parameter in your DB parameter group and reboot the instance for the change to take effect.
If you've checked all these points and are still not seeing the metrics, it would be advisable to contact AWS support. They can provide more specific assistance and investigate if there are any underlying issues with the Performance Insights service for your particular RDS instance.
Remember, Performance Insights can sometimes report '0.00' or '-' (unknown) for SQL statistics under certain conditions, such as when only one sample exists or when two samples have the same values. This is normal behavior and doesn't necessarily indicate a problem with your setup.
Sources
Aurora performance insights not showing calls/sec Avg latency and rows examined | AWS re:Post
Performance Insights in RDS can't show the call/sec, Avg latency (ms)/call... | AWS re:Post
SQL statistics for RDS PostgreSQL - Amazon Relational Database Service
Analyzing queries with the Top SQL tab in Performance Insights - Amazon Relational Database Service
Relevant content
asked 3 years ago
