mirror of
https://github.com/prometheus/prometheus.git
synced 2024-09-20 07:47:31 -07:00
1cfc8f65a3
This is a bit more conservative than we could be. As long as a chunk isn't the first in a block, we can be pretty sure that the previous chunk won't disappear. However, the incremental gain of returning NotCounterReset in these cases is probably very small and might not be worth the code complications. Wwith this, we now also pay attention to an explicitly set counter reset during ingestion. While the case doesn't show up in practice yet, there could be scenarios where the metric source knows there was a counter reset even if it might not be visible from the values in the histogram. It is also useful for testing. Signed-off-by: beorn7 <beorn@grafana.com> |
||
|---|---|---|
| .. | ||
| fuzz-data | ||
| parser | ||
| testdata | ||
| bench_test.go | ||
| engine.go | ||
| engine_test.go | ||
| functions.go | ||
| functions_test.go | ||
| fuzz.go | ||
| fuzz_test.go | ||
| promql_test.go | ||
| quantile.go | ||
| query_logger.go | ||
| query_logger_test.go | ||
| test.go | ||
| test_test.go | ||
| value.go | ||
| value_test.go | ||