@sundsta thanks for pointing me to sharding. The documentation for it is pretty bare, so I'm wondering if it's possible to version queries, then have, say, 95% of hosts on v0, 5% of hosts on v1 of the query, and slowly shift the rollout percentage to have v1 have 100% rollout and v0 have 0%. As far as I can see, sharding is amazing for new queries, where you can slowly roll them out to the fleet, but it doesn't really do a good job for changing existing queries, where you want the query to have the same name (for alerts in logs, etc).

Not currently possible as far as I know, but i can see the appeal. Maybe submit a PR or feature request?

Yup, I will raise a feature request. Unfortunately I don't have time to work on it right now as I've got piles of other plates in the air 😐