I'm trying to enable Performance Insights in Amazon Relational Database Service (Amazon RDS) for MySQL. Why can't I access the data?
You might not be able to access or view your data in Performance Insights in Amazon RDS for MySQL for the following reasons:
- You've tried to manually set the Performance Schema values in a parameter group.
- Your DB instance doesn't have enough resources to access the data from Performance Insights.
- There's a transient networking issue, or system maintenance is underway on your DB instance.
- You've performed an upgrade of your DB instance from an unsupported Performance Insights version to a supported version.
- The data load on your MySQL DB instance is below the database load threshold.
You've tried to manually set the Performance Schema values in a parameter group
If you tried to manually update the Performance Schema parameter values in a parameter group, then Performance Insights won't work properly. A list of detailed wait events won't appear.
The following parameters can't be automatically updated by Performance Insights:
- performance-schema-consumer-events-waits-current: ON
- performance-schema-instrument: wait/%=ON
- performance-schema-consumer-global-instrumentation: ON
- performance-schema-consumer-thread-instrumentation: ON
Note: You can reset the Performance Schema parameters back to the default values. After resetting the values, make sure to reboot your DB instance to enable the Performance Schema.
Your DB instance doesn't have enough resources to access the data from Performance Insights
If your DB instance is experiencing a heavy load, then your resources are dedicated to the database process. As a result, system processes such Performance Insights are deprioritized. To check whether your DB instance is under a heavy load, review the CPU utilization, disk queue depth, and read write latency values in Amazon CloudWatch.
If your MySQL DB instance is experiencing a heavy load, then consider vertically scaling your DB instance class. When you configure a DB instance class, there will be some downtime. To troubleshoot CPU usage issues, see How can I troubleshoot and resolve high CPU utilization on my Amazon RDS for MySQL instances?
There's a transient networking issue, or system maintenance is underway on your DB instance
When your DB instance experiences a transient networking issue or system maintenance, Performance Insights might not properly report data. If these factors affect your resources, then review the Personal Health Dashboard. The Personal Health Dashboard will provide guidance on how to proceed.
You've performed an upgrade of your DB instance from an unsupported Performance Insights version to a supported one
If you enable Performance Insights while performing a DB engine version upgrade, then your DB instance might not properly apply these changes. Also, make sure that your Amazon RDS Performance Insights version is supported, or your data might not properly sync.
If your MySQL DB engine version is supported, then you can enable or disable Performance Insights when creating an instance or when modifying an instance. Make sure to choose Apply Immediately to apply the changes right away.
Performance Insights is available only for MySQL DB engine versions 8.0.17 and higher, version 5.7.22 and higher, and version 5.6.41 and higher. Additionally, Performance Insights isn't supported on the following DB instance classes: db.t2.micro, db.t2.small, db.t3.micro, and db.t3.small. Therefore, check to make sure that your MySQL DB engine version is compatible. For more information about supported DB engine versions for Performance Insights, see Amazon RDS DB engine support for Performance Insights.
The data load on your MySQL DB instance is below the database load threshold
If you enabled Performance Insights and you can't view your data, then check the Db load chart and Counter metrics in your Performance Insights dashboard. If you see data under Counter metrics, but not Db load chart, then your DB load might be below the database load threshold for MySQL. To test and confirm, run a long-running transaction on your MySQL DB instance, and then check the Performance Insights dashboard again. If the data populates, then your original data load is likely below the data load threshold.