New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate scoring slow query plans from auto_explain with pgMustard #9
Comments
In the interim, if you're interested in configuring auto_explain for use with pgMustard (or in general, for that matter), we've written up a guide: https://www.pgmustard.com/auto-explain |
We've decided to start with an even simpler first step here — send a plan to a pgMustard endpoint, and it'll return the tip scores, as well as some other top-level info. This should allow for similar use cases mentioned initially (e.g. automated prioritisation) albeit with more of the work on your side, as well as at least one use case I hadn't considered initially (forever grateful for creative customers!). We have a private beta available, please get in touch if you'd like to give it a go. |
We've now shipped the v1 of this, and made it available in the Team and Company plans 🎉 I've added a new issue for the longer term vision, please do chime in there if you'd like to see us head in that direction :) |
We've heard from several people that they'd like to be able to automatically send slow query plans to pgMustard, for example from the logs, via auto_explain. This could in time lead to some other cool features.
Our first step would be adding a simple API that could accept plans, and surface them in a "history" view of sorts. After that we could start to surface where the biggest wins could be, and help people become more proactive.
The text was updated successfully, but these errors were encountered: