After a crazy travel week, hopping from NYC to Chicago to Poland and back home, I wanted to get out the little bibs and bobs that I had worked on while I was traveling. This is not a big huge groundbreaker of a release, but I'm happy that anything got done considering the craziness. Full release notes are below. Happy monitoring, you crazy kids.
Sometimes Taco Tuesday turns into Most Margaritas Monday and then you forget to post your release until Wet Brain Wednesday. Ah well. Some you win, some you lose.
A very special thank you to everyone who submits issues and contributes code. In this release, rferraton and ClaudioESSilva got some pretty cool new stuff in. The full change log is below, but the Query Store integration is quickly becoming the star of the show in a lot of ways. It's almost like a self-contained monitoring tool at this point.
There's a web version of the plan analysis portion of the app too. This is useful for people who want to give things a test drive, or who can't download an executable. The plan analysis is all client-side. You completely control whether and when the plan gets uploaded for sharing, and how long it remains available for. I have no interest in your XML unless you're paying me.
This week I'm off to Pass Summit East in Chicago, and SQLDay in Wroclaw, Poland. One after the other. Last week I was in Florida for Data Saturday Jacksonville. Hopefully that explains why this week's release is a) early and b) pretty light on changes. It will also hopefully explain why there won't be a release next week. I can see, hear, smell, and feel your hearts breaking on that news.
So while I'm off spending all my Zlotys on Okocim and Kielbasa, you can just imagine that the CPU spikes you see in this here monitoring tool is about what my blood pressure and cholesterol are doing.
The ongoing work to make this simpler to add rules/information about things in plans will eventually allow users to extend things to deal gracefully with local issues. Right now I'm not sure how it will go. For informational bits like wait stats, it's very easy. For arbitrarily complex rules, it's a bit harder to jam those into a json config file that can be interpreted correctly and consistently.
Anyway, as always, thank you to my valuable contributors of code, and Joe Obbish for the high quality feedback.
If you have any questions, comments, concerns, ideas, or you'd like to support this project, head over here.
I seem to recall there being some super-shifting feature getting added for 2.0 and 2.5 versions. As we approach 3.0, I don't quite have one of those ready.
I'm also starting to wonder if the weekly releases are still necessary. That's a bit of a relief, to be honest. For a bit it felt like I was shipping big fixes and changes at a frantic pace. Now I'm half-tempted to start labeling things "stable" or "LTS" or "dude-trust-me".
Anyway, changelog and all that is below.
If you want to chime in on the future of Full/Lite dashboards, check out this discussion.
If you want to report an issue, request a feature, or pitch in some code, head over here.