mirror of
https://github.com/prometheus/prometheus.git
synced 2024-11-18 03:24:05 -08:00
c35f138a9a
It's a prefectly valid use case to have a sparse histogram with a zero threshold of zero (i.e. only observations of exactly zero go into the zero bucket). Even if the current PoC implementation of client_golang doesn't allow that, such a case should be ingested properly. However, there is now the edge case af a sparse histogram with a zero threshold of zero and no observations yet. Such a histogram would look the same if it was meant to be a conventional histogram. For now, we ingest this case as a conventional histogram, but the final format should have means to unambiguously express if a histogram is meant to be ingested as a sparse histogram or as a conventional histogram. Signed-off-by: beorn7 <beorn@grafana.com> |
||
|---|---|---|
| .. | ||
| exemplar | ||
| gate | ||
| histogram | ||
| labels | ||
| logging | ||
| modtimevfs | ||
| pool | ||
| relabel | ||
| rulefmt | ||
| runtime | ||
| textparse | ||
| timestamp | ||
| value | ||