- 25 4月, 2017 2 次提交
-
-
由 Fabian Reinartz 提交于
Preserve Alertmanager URLs as *url.URL.
-
由 David Symonds 提交于
Render a nicer link in the web UI.
-
- 24 4月, 2017 1 次提交
-
-
由 Conor Broderick 提交于
-
- 19 4月, 2017 3 次提交
-
-
由 Brian Brazil 提交于
Merge 1.6.1 release from 1.6 branch
-
由 Brian Brazil 提交于
-
由 beorn7 提交于
-
- 18 4月, 2017 2 次提交
-
-
由 Björn Rabenstein 提交于
storage: Don't panic if storage has no FPs even after initial wait
-
由 beorn7 提交于
-
- 16 4月, 2017 1 次提交
-
-
由 Matt Layher 提交于
-
- 15 4月, 2017 7 次提交
-
-
由 Tobias Schmidt 提交于
-
由 Tobias Schmidt 提交于
Simplify promlint problems gathering, use protobuf accessors
-
由 Matt Layher 提交于
-
由 Matt Layher 提交于
-
由 Matt Layher 提交于
-
由 Björn Rabenstein 提交于
Cut v1.6.0
-
由 beorn7 提交于
-
- 14 4月, 2017 2 次提交
-
-
由 Jack Neely 提交于
* Force buckets in a histogram to be monotonic for quantile estimation The assumption that bucket counts increase monotonically with increasing upperBound may be violated during: * Recording rule evaluation of histogram_quantile, especially when rate() has been applied to the underlying bucket timeseries. * Evaluation of histogram_quantile computed over federated bucket timeseries, especially when rate() has been applied This is because scraped data is not made available to RR evalution or federation atomically, so some buckets are computed with data from the N most recent scrapes, but the other buckets are missing the most recent observations. Monotonicity is usually guaranteed because if a bucket with upper bound u1 has count c1, then any bucket with a higher upper bound u > u1 must have counted all c1 observations and perhaps more, so that c >= c1. Randomly interspersed partial sampling breaks that guarantee, and rate() exacerbates it. Specifically, suppose bucket le=1000 has a count of 10 from 4 samples but the bucket with le=2000 has a count of 7, from 3 samples. The monotonicity is broken. It is exacerbated by rate() because under normal operation, cumulative counting of buckets will cause the bucket counts to diverge such that small differences from missing samples are not a problem. rate() removes this divergence.) bucketQuantile depends on that monotonicity to do a binary search for the bucket with the qth percentile count, so breaking the monotonicity guarantee causes bucketQuantile() to return undefined (nonsense) results. As a somewhat hacky solution until the Prometheus project is ready to accept the changes required to make scrapes atomic, we calculate the "envelope" of the histogram buckets, essentially removing any decreases in the count between successive buckets. * Fix up comment docs for ensureMonotonic * ensureMonotonic: Use switch statement Use switch statement rather than if/else for better readability. Process the most frequent cases first.
-
由 Matt Layher 提交于
-
- 12 4月, 2017 1 次提交
-
-
由 Conor Broderick 提交于
Added min/max to graph to accommodate constant time series
-
- 11 4月, 2017 5 次提交
-
-
由 Björn Rabenstein 提交于
Vendoring update prior to 1.6 release
-
由 beorn7 提交于
-
由 beorn7 提交于
This is mostly required to enable summaries without quantiles
-
由 beorn7 提交于
-
由 Brian Brazil 提交于
-
- 08 4月, 2017 1 次提交
-
-
由 Björn Rabenstein 提交于
storage: Several optimizations of checkpointing
-
- 07 4月, 2017 13 次提交
-
-
由 Goutham Veeramachaneni 提交于
* Test Longer Tests in Travis Signed-off-by: NGoutham Veeramachaneni <cs14btech11014@iith.ac.in> * Make test Target Run All Tests * Add test-short to run short tests test is running all the tests now as we are running make tests in CircleCI and I think the base image is shared across Prometheus Org. Signed-off-by: NGoutham Veeramachaneni <cs14btech11014@iith.ac.in> * Remove Empty Line Signed-off-by: NGoutham Veeramachaneni <cs14btech11014@iith.ac.in>
-
由 beorn7 提交于
-
由 beorn7 提交于
- checkpointSeriesMapAndHeads accepts a context now to allow cancelling. - If a shutdown is initiated, cancel the ongoing checkpoint. (We will create a final checkpoint anyway.) - Always wait for at least as long as the last checkpoint took before starting the next checkpoint (to cap the time spending checkpointing at 50%). - If an error has occurred during checkpointing, don't bother to sync the write. - Make sure the temporary checkpoint file is deleted, even if an error has occurred. - Clean up the checkpoint loop a bit. (The concurrent Timer.Reset(0) call might have cause a race.)
-
由 Björn Rabenstein 提交于
storage: Recover from corrupted indices for archived series
-
由 Goutham Veeramachaneni 提交于
-
由 Julius Volz 提交于
Add triton zone brand metadata
-
由 Björn Rabenstein 提交于
storage: Guard against a corner case of data corruption
-
由 Björn Rabenstein 提交于
storage: Guard against appending to evicted chunk
-
由 Tom Wilkie 提交于
* Remote writes: retry on recoverable errors. * Add comments * Review feedback * Comments * Review feedback * Final spelling misteak (I hope). Plus, record failed samples correctly.
-
由 Richard Kiene 提交于
-
由 beorn7 提交于
Fixes #2480. For certain definition of "fixes". This is something that should never happen. Sadly, it does happen, albeit extremely rarely. This could be some weird cornercase we haven't covered yet. Or it happens as a consequesnce of data corruption or a crash recovery gone bad. This is not a "real" fix as we don't know the root cause of the incident reported in #2480. However, this makes sure the server does not crash, but deals gracefully with the problem: The series in question is quarantined, which even makes it available for forensics.
-
由 beorn7 提交于
Fixes #2475.
-
由 beorn7 提交于
An unopenable archived_fingerprint_to_timerange is simply deleted and will be rebuilt during crash recovery (wich can then take quite some time). An unopenable archived_fingerprint_to_metric is not deleted but instructions to the user are logged. A deletion has to be done by the user explicitly as it means losing all archived series (and a repair with a 3rd party tool might still be possible).
-
- 06 4月, 2017 2 次提交
-
-
由 Julius Volz 提交于
Separate out remote read responses.
-
由 Conor Broderick 提交于
-