mirror of
https://github.com/prometheus/prometheus.git
synced 2024-09-20 07:47:31 -07:00
67274f0794
This means that if there is no stale marker, only the usual staleness delta (5m) applies. It has occured to me that there is an oddity in the heurestic. It works fine as long as you have 2 points within the last 5m, but breaks down when the time window advances to the point where you have just 1 point. Consider you had points at t=0 and t=10. With the heurestic it goes stale at t=51, up until t=300. However from t=301 until t=310 we only see the t=10 point and the series comes back to life. That is not desirable. I don't see a way to keep this form of heurestic working given this issue, so thus I'm removing it. |
||
|---|---|---|
| .. | ||
| fuzz-data | ||
| testdata | ||
| ast.go | ||
| bench_test.go | ||
| engine.go | ||
| engine_test.go | ||
| functions.go | ||
| functions_test.go | ||
| fuzz.go | ||
| lex.go | ||
| lex_test.go | ||
| parse.go | ||
| parse_test.go | ||
| printer.go | ||
| printer_test.go | ||
| promql_test.go | ||
| quantile.go | ||
| test.go | ||
| test_test.go | ||
| value.go | ||