Chris LuandGitHub 6832b76529 telemetry: key per-cluster value gauges by cluster_id only (#10397) ...

telemetry: key value gauges by cluster_id only

The value gauges were labeled {cluster_id, version, os}, so a cluster
reporting back after an upgrade started a new series while the old one
kept its last value forever: sum() double-counted every upgraded
cluster, and per-cluster history broke at every version change.

Key the five value gauges by cluster_id alone so each cluster keeps one
continuous series across upgrades; version/os metadata stays on
cluster_info (deleted and re-set on change), available to value queries
via 'on(cluster_id) group_left' joins. Update README accordingly.

2026-07-22 17:41:27 -07:00

..

api

fix(telemetry): use correct TopologyId field in integration test (#8714)

2026-03-20 22:15:05 -07:00

dashboard

remove features and deployments fields

2025-06-28 20:03:06 -07:00

storage

telemetry: key per-cluster value gauges by cluster_id only (#10397)

2026-07-22 17:41:27 -07:00

Dockerfile

REFACTOR: Update telemetry deployment docs and README for new Docker flow (#7250)

2025-09-18 14:10:01 -07:00

go.mod

telemetry: tidy server module after prometheus bumps (#10380)

2026-07-20 23:13:27 -07:00

go.sum

telemetry: tidy server module after prometheus bumps (#10380)

2026-07-20 23:13:27 -07:00

main.go

add telemetry (#6926)

2025-06-28 14:11:55 -07:00

Makefile

add telemetry (#6926)

2025-06-28 14:11:55 -07:00