Number tile on a gauge changes with the time range: `sum` adds up every sample in short ranges

Aperta
#3,500 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
70/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
clickhouse, typescript

Direzione di ricerca

Start with the gauge CTE and number-tile aggregation in packages/common-utils/src/core/renderChartConfig.ts, especially the linked lines, then read renderChartConfig.int.test.ts for the integration-test pattern. Reproduce the supplied two-series gauge case with short and six-hour ranges. Done means the number tile returns the same result for both ranges, using each series’ last value before aggregating across series.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

external

What happened?

A number tile over the same gauge data gives a different value depending on how wide the time range is.

Data: two gauge series, one point a minute for 10 minutes. Their latest values are 80 and 4. Number tile, aggFn: sum, on main (2bfc630):

Time range (contains the same 10 minutes of data) Result
exactly the 10 minutes 515.75: every sample summed
6 hours 84: the latest value per series
7 days 84

A number tile has no granularity, so the gauge CTE buckets the data at 'auto' granularity, which is derived from the date range. It takes LastValue per series per bucket, and the outer aggregation then runs over all the buckets. A short range gives small buckets, and in the end one bucket per sample:

Expected: the same data gives the same number for any range that contains it. For a gauge, that would be the last value of each series in the range, then the aggregation across series (84 here). That matches a PromQL instant query, and the last point of the same chart as a line.

We only tested sum. avg, min and max go through the same CTE, so we expect them to change with the range too, just less visibly.

Steps to reproduce

Reproduces on play.hyperdx.io? Didn't try.

An integration test in the style of renderChartConfig.int.test.ts, on main:

  1. Insert gauge repro.cpu for hosts a (50, 25, 12.5, 6.25, 100, 75, 10, 80, 40, 80) and b (1, 2, 3, 4, 5, 6, 5, 4, 3, 4), one point a minute.
  2. renderChartConfig with displayType: Number, select: [{ aggFn: 'sum', metricType: 'gauge', metricName: 'repro.cpu', valueExpression: 'Value' }], no granularity.
  3. dateRange = the 10 minutes → 515.75. dateRange = 6 h ending at the same point → 84.

How are you running HyperDX?

Helm (ClickStack chart 2.1.0) with the hyperdx:2-nightly image (2.42.0 plus the Node bump from #3456), our own ClickHouse 26.2.5.45. Reproduced on main 2bfc630.

Where does it show up?

Dashboard number tiles. We hit it while rebuilding dashboards through the MCP tools: a "connected clients" tile (sum of a per-pod Redis gauge) showed a multiple of the real count, so we rebuilt it in SQL.

Debug info

N/A.

Logs

None.


Written with help from an AI assistant (Claude Code). The behaviour comes from our own deployment and an integration test on main.

Lingua principale
TypeScript
Stelle
10.1k
Fork
527
Merge medio
1g 20h
PR unite (30g)
186

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ClickHouse/ClickStack

Tutte le issue di ClickHouse/ClickStack

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.