Minor Changes

• 8a9fcd2f: feat: Support macros in PromQL charts
• 08d9a908: feat: Plot several PromQL expressions on one chart
• d9e2c58b: Add a per-source floor for auto granularity. A metric source can now set "Minimum auto granularity" (Team Settings → Sources → your Metrics source) so that auto-inferred time buckets never go below it — useful when the underlying metric is reported on a fixed interval (e.g. a 60s scrape), since a short selected date range can otherwise auto-infer a smaller bucket than that interval and render a sparse/steppy series (alternating real-sample/empty buckets). Mirrors Grafana's per-datasource "Min interval" setting. Unset (the default) preserves the existing unfloored behavior, and an explicit (non-auto) granularity chosen on a tile is never affected.

Patch Changes

• 1e355ac4: fix: don't scan the whole table to discover Map keys

  getMapKeys only applied a time predicate when the caller passed both a date range and a timestamp expression; otherwise the raw sampledKeys scan ran with no WHERE and touched every part of the table. It now defaults a missing date range to the last 24 hours and skips the raw scan entirely when there is no timestamp expression to filter on. The chart, alert and dashboard-filter editors pass the source and date range they already have so Map keys keep autocompleting there.

• 793fe19e: feat: Substitute dashboard variables in markdown tiles

• ec4f5087: fix: allow grouping gauge and sum metric charts by materialized and alias columns

  Grouping or selecting a MATERIALIZED or ALIAS column on a gauge or sum metric chart failed with Unknown expression identifier, because the intermediate query didn't carry those columns through.

• a8a72c11: fix: Support instant queries and reductions on PromQL number tiles

• 8cfb2672: feat: Support background sparklines on PromQL range number tiles

• 4570d5ee: feat: Support pie and bar tiles on PromQL sources

• 78ed5921: feat: Support table tiles on PromQL sources

• 23423c13: fix: Show distribution only labels a value "<1%" when the sample shows it is rare, not when it has no matching rows, and shows 100% when the field's filter allows only that value

• 19182e7e: fix: only split a query at a standalone SETTINGS keyword

  extractSettingsClauseFromEnd cut the query at the first "settings" anywhere in it, including inside a string or an identifier. A multi-series metric chart with a metric such as app.settings.reloads produced SQL with an unterminated string, and a SQL filter on a column such as AppSettings was rewritten to reference App. The keyword now has to stand alone outside quotes.