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

Ouverte
#3,500 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
70/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
clickhouse, typescript

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
10.1k
Forks
527
Merge moyen
1 j 20 h
PR mergées (30 j)
186

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ClickHouse/ClickStack

Toutes les issues de ClickHouse/ClickStack

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.