Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upMake rule evaluation and federation consistent in time #1893
Comments
This comment has been minimized.
This comment has been minimized.
|
Also #1887 for the reported incident that caused the discussion in the first place. |
ncabatoff
added a commit
to ncabatoff/prometheus
that referenced
this issue
Aug 25, 2016
brian-brazil
referenced this issue
Apr 7, 2017
Closed
Aggregated histogram_quantile produces incorrect, unstable results #2598
This comment has been minimized.
This comment has been minimized.
lmb
commented
Apr 11, 2017
|
I reported #2598, which was closed as a duplicate of this issue. I think this issue should mention that this behaviour breaks aggregating histograms using histogram_quantile in the currently released version. That should prevent more dupes. |
This comment has been minimized.
This comment has been minimized.
|
AFAICS, this is fixed 2.0. Can this be closed @fabxc @brian-brazil |
This comment has been minimized.
This comment has been minimized.
|
This is not fixed in 2.0 (yet). |
This comment has been minimized.
This comment has been minimized.
|
I've got a basic version of this working over in the tsdb repo, it needs cleanup and performance work. |
brian-brazil
added
not-as-easy-as-it-looks
priority/P2
labels
Jul 14, 2017
brian-brazil
self-assigned this
Jul 14, 2017
shollingsworth
referenced this issue
Apr 13, 2018
Merged
Treat custom textfile metric timestamps as errors #769
This comment has been minimized.
This comment has been minimized.
|
@beorn7 , @brian-brazil , @gouthamve is this issue still unsolved? |
This comment has been minimized.
This comment has been minimized.
|
Yes, there's an old PR over in TSDB for this. I believe @gouthamve was planning on working on it soon. |
This comment has been minimized.
This comment has been minimized.
|
aah that must be the isolation PR prometheus/tsdb#306 |
beorn7 commentedAug 15, 2016
Currently, if samples get ingested during a rule is evaluated or a federation request is processed, only a subset of samples with the same timestamp may be taken into account during the evaluation.
Making ingestion of all the samples from a single scrape atomic would solve the problem, but the problem might be solved in an easier way by "simply" ignoring samples that came in after a certain watermark.
For reference: discussion started in prometheus/docs#514 and already referenced #398 as a possible part of the solution.