Troubleshooting
This page contains troubleshooting information for common issues we see when setting up and running OtterTune.

Why does OtterTune show that MySQL's throughput is always 0?

OtterTune uses the transaction counters from MySQL to calculate the throughput. To collect them, you need to add module_trx to the list of modules specified by the innodb_monitor_enable knob. After updating this knob, you should start seeing throughput measurements after a few minutes. Please see the documentation for more information.

Why does OtterTune show that P99QueryLatency is always 0?

  1. 1.
    Please check if your agent version >= 0.3.0. If not, you should upgrade your agent.
  2. 2.
    Please make sure you configure the database correctly. Postgres requires to load the module pg_stat_statements, and MySQL requires to enable Performance Insights.
  3. 3.
    Please make sure the database user has permissions to collect query latencies.

My OtterTune Agent created with CloudFormation is not working. How do I see what is going wrong?

  1. 1.
    Navigate to the CloudFormation AWS Console
  2. 2.
    Look for an OtterTune Agent stack. If CloudFormation was able to create the stack succesfully the status will be CREATE_COMPLETE.
  3. 3.
    If something has gone wrong, select the stack and click on the events tab to see more details. Fixing the stack will require you to delete the existing stack and then restart the Agent creation process on the OtterTune website. Select the database you are connecting, go to settings -> View Agent Setup info.
  4. 4.
    If the stack was created succesfully but you are still seeing issues, navigate to the ECS Cluster AWS Console. Select the OtterTune agent cluster, select the OtterTune agent service, and select logs to see Agent output. If you would like help interpreting any failures there please reach out to Support.
Last modified 11h ago