OtterTune Ideas

Should be quite similar to RDS for MySQL tuning

Currently the suggestion for dropping unused indexes does not use the CONCURRENTLY keyword. This means it acquires an ACCESS EXCLUSIVE lock on the table, blocking other accesses until the index drop can be completed. Using CONCURRENTLY avoids this issue.

I'd like to see Ottertune suggest indexes that should be created based on the queries that are running.

Add the ability to see all members of the organization, their invitation status (Accepted, Declined, etc.), and who invited each team member.

Using OtterTune's Public API, enable the ability to programmatically send/create Jira tasks from OtterTune's actionable recommendations and failed health checks.

Recently we released v0 of Database Trends and Workload Characterization. We plan to further utilize the comparative metrics currently being collected to surface more information about users' databases and how they compare to databases with similar engines, engine versions, and instance sizes.

This work includes UXUI improvements, as well as backend improvements that feed more accurate metrics about configuration sources.

Previously, to err on the side of caution, we would disable auto-tuning when certain changes were detected, such as major version or hardware changes. Based on customer feedback, we now adjust the necessary elements and communicate this change to affected users so tuning is no longer interrupted.

Include Schema Change events in the Event Log

Level up the Query Recommendations to include:Rewriting failed queriesViewing all queries, not just long-running queries that fail checksViewing specific line item(s) where issues are found