Minor Changes
- 8a9fcd2: feat: Support macros in PromQL charts
- 08d9a90: feat: Plot several PromQL expressions on one chart
- d9e2c58: 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
-
1e355ac: fix: don't scan the whole table to discover Map keys
getMapKeysonly applied a time predicate when the caller passed both a date
range and a timestamp expression; otherwise the rawsampledKeysscan ran with
noWHEREand 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. -
793fe19: feat: Substitute dashboard variables in markdown tiles
-
ec4f508: 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. -
a8a72c1: fix: Support instant queries and reductions on PromQL number tiles
-
8cfb267: feat: Support background sparklines on PromQL range number tiles
-
4570d5e: feat: Support pie and bar tiles on PromQL sources
-
78ed592: feat: Support table tiles on PromQL sources
-
23423c1: 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
-
19182e7: fix: only split a query at a standalone SETTINGS keyword
extractSettingsClauseFromEndcut 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 asapp.settings.reloadsproduced SQL with an unterminated
string, and a SQL filter on a column such asAppSettingswas rewritten to
referenceApp. The keyword now has to stand alone outside quotes.