- Newest
- Most votes
- Most comments
Kindly perform below checks and let me know your findings
- Check Scheduled Tasks
- Examine Connections
- Analyze the query running at the time of the spikes
- Review Auto Scaling Policy
- Check if any external services or utility is connected to the database
- Check Capacity Settings
If something is happening that is not tied in to SQL processing, that could be some memory or CPU usage happening in the underlying operating system. I suggest turning on Enhanced Monitoring (EM) and looking at what's happening at the operating system level.
I have seen where SQL submitted through Data API didn't show up in Performance Insights. So check if there any Lambda functions running that might be submitting requests through Data API. I like to use CloudTrail and filter by specific time windows to find things like Lambda functions I forgot were still running. Also check if there are any pg_cron scheduled jobs on the Postgres server, in addition to regular cron jobs on the client systems.
Relevant content
- asked a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
Yes, I have checked all of the points mentioned. There is no such anomaly or pattern.