How do I troubleshoot issues that occur when I activate Performance Insights on my Amazon Aurora MySQL DB instance?

Resolution

Check your engine versions and requirements

Before you activate Performance Insights for Aurora, make sure that you're running a supported Aurora DB engine and DB instance class. For Aurora MySQL-Compatible, you must run the 2.04.2 or later 2.x versions that are compatible with MySQL 5.7.

Note: There are additional engine requirements for Aurora DB clusters that allow for parallel queries.

After you check requirements, activate Performance Insights on your DB instance. If you still encounter issues, then take following troubleshooting actions to resolve common errors.

You can't see Performance Schema detailed wait events on your Performance Insights dashboard

If you manually activated the performance_schema parameter in your parameter group, then reset the parameter. Then, modify your instance to turn Performance Insights on and then off.

Note: When you turn Performance Insights on or off, you don't experience downtime, reboots, or failovers.

Performance Insights automatically manages and sets the following parameters:

• performance_schema=1
  Note: The source parameter is set to engine-default.
• performance-schema-consumer-events-waits-current=ON
• performance-schema-instrument: wait/%=ON
• performance_schema_consumer_global_instrumentation=ON
• performance_schema_consumer_thread_instrumentation=ON

You can't use a custom parameter group to configure the preceding parameters. If you manually configure the performance_schema parameter on the cluster to active Performance Insights, then you might lose data points.

You can't see your entire query on your Performance Insights dashboard

The Performance Insights dashboard has a quota for maximum text size. If your text exceeds the quota, then you can't view the entire query.