4 ms·
It seems to me like an anti-pattern to have a time series where the identity is formed by (device,location,firmware version,sensor). It seems to me like (device
by jeffbee 5y ago
It seems to me like an anti-pattern to have a time series where the identity is formed by (device,location,firmware version,sensor). It seems to me like (device,location,sensor) is fine identity for an original of, presumably, real-valued time series data, while (device,location,firmware) is a good identity for, I guess, a string-valued time series, and if you really needed to get sensor data aggregated by firmware version you'd do a join in this rare and in my opinion highly contrived case.
- Something1234 5y agoMaybe you want to be able to detect data errors when updating firmware versions? But there should be a way to compute firmware version of a device with some kind of join, maybe device updates?
- chucky_z 5y agowhat you do instead is have an extra metric entirely per device. it's easier to have 1000 extra metrics than an extra label worth of cardinality on 1,000,000 metrics for every single update. within prom: cpu{hostname,metadata,cpu_socket} 5.0 cpu{hostname,metadata,cpu_socket} 6.0 cpu{hostname,metadata,cpu_socket} 5.0 cpu{hostname,metadata,cpu_socket} 4.0 version{hostname,version_number} 1.0 instead of baking version_number in everywhere. just as an example, then you can know "oh, hostname has version number" on a chart, or even do some inversions and say "count of version number" to find stragglers.