prometheus

Commit Graph

Author	SHA1	Message	Date
Bryan Boreham	5710ddf24f	[ENHANCEMENT] Alerts: remove metrics for removed Alertmanagers (#13909 ) * [ENHANCEMENT] Alerts: remove metrics for removed Alertmanagers So they don't continue to report stale values. Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 months ago
Björn Rabenstein	751100b3d0	Merge pull request #12998 from ringerc/docs-instant-vector-staleness Docs: Refer to staleness in instant vector documentation	2 months ago
Craig Ringer	15b68e989c	Refer to staleness in instant vector documentation The instant vector documentation does not explain which metric samples are selected - in particular, it makes no reference to staleness. It's confusing when reading the docs to understand how exactly Prometheus selects the metrics to report: the most recent sample older than the search timestamp specified in the API request, so long as that metric is not "stale". Signed-off-by: Craig Ringer <craig.ringer@enterprisedb.com>	2 months ago
Bryan Boreham	5d8f0ef0c2	Merge pull request #14721 from bboreham/exp-grow-postings [PERF] TSDB: Grow postings by doubling	2 months ago
Julius Volz	5037cf75f2	Merge pull request #14972 from prometheus/jvp/make-mantime-ui-assets-relative UI: Make mantime UI assets relative	2 months ago
Björn Rabenstein	67caa03dc1	Merge pull request #14970 from prometheus/beorn7/doc docs: Improve, clarify, and fix documentation on scrape limits	2 months ago
Jesus Vazquez	cb4bc5e786	UI: Make mantime UI assets relative Signed-off-by: Jesus Vazquez <jesusvzpg@gmail.com>	2 months ago
beorn7	a9243d4d2c	docs: Improve, clarify, and fix documentation on scrape limits In detail: - Clarify that label name and value length limits are in byte, not in UTF-8 data points. - More consistent formatting to keep 80 characters line limet. - Clarify various misleading specifications around "per sample", "per scrape", "per scrape config", "per job"... - Fix grammar. Signed-off-by: beorn7 <beorn@grafana.com>	2 months ago
Bryan Boreham	a0f26febc2	Merge pull request #12180 from damnever/perf/relabel-add-label Optimize constant label pair adding from relabeling.	2 months ago
Arve Knudsen	c2bbabb4a7	promql.Engine: Refactor vector selector evaluation into a method (#14900 ) * PromQL.Engine: Refactor Matrix expansion into a method Add utility method promql.evaluator.expandSeriesToMatrix, for expanding a slice of storage.Series into a promql.Matrix. Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com> * Rename to generateMatrix Rename evaluator.expandSeriesToMatrix into generateMatrix, while also dropping the start, end, interval arguments since they are evaluator fields. Write more extensive method documentation. Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com> * Rename to evalVectorSelector Rename to evalVectorSelector after discussing with @michahoffmann. Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com> --------- Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com>	2 months ago
Bryan Boreham	faf5ba29ba	Merge pull request #14959 from prometheus/merge-2.55-into-main Merge 2.55 into main	2 months ago
Arve Knudsen	3f9b869fb5	Fix react-app (old UI) package-lock.json cd web/ui/react-app npm install Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com>	2 months ago
George Krajcsovits	f179cb948b	chore: bump client_golang from 1.20.3 to 1.20.4 (#14963 ) Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>	2 months ago
Julien	919648cafc	Merge pull request #14947 from roidelapluie/reloadinvalidyaml fix(autoreload): Reload invalid yaml files	2 months ago
Bryan Boreham	4c90118361	Remove CHANGELOG duplicate line Signed-off-by: Bryan Boreham <bjboreham@gmail.com> #14402 is the issue and #14403 is the fix.	2 months ago
Bryan Boreham	ca673eb749	Merge remote-tracking branch 'origin/release-2.55' into merge-2.55-into-main Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 months ago
Bryan Boreham	e3f5c7c2a0	[Release 2.55] Update CHANGELOG Make text more consistent with 3.0 branch Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 months ago
Bryan Boreham	31c5760551	Neater string vs byte-slice conversions (#14425 ) unsafe.Slice and unsafe.StringData were added in Go 1.20 Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 months ago
Arthur Silva Sens	6bcb064d93	Merge pull request #14950 from Maniktherana/fuzz-om-minor-change chore: remove unused code	2 months ago
Julius Volz	52fe4cc4ee	Merge pull request #14944 from roidelapluie/copy Mantine UI: removed unuse file	2 months ago
Julius Volz	dfc6f4b5bc	Merge pull request #14945 from roidelapluie/submillis fix(web): properly format sub-millisecond durations in target status page	2 months ago
Bryan Boreham	e0260930d6	Merge pull request #14951 from prometheus/update-rel-2.55 [release-2.55] Add #14948 to rc0	2 months ago
Bryan Boreham	d42232e178	Merge pull request #14932 from bboreham/chunk-xor-combine-writebits [PERF] TSDB: Chunk encoding: shorten some write sequences	2 months ago
Bryan Boreham	e3617cbd2c	Add #14948 to CHANGELOG Also update the date of the RC which hasn't gone out yet. Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 months ago
Bryan Boreham	6f0d6038b7	[BUGFIX] TSDB: Only query chunks up to truncation time (#14948 ) If the query overlaps the range currently undergoing compaction, we should only fetch chunks up to that time. Need to store that min time in `HeadAndOOOIndexReader`. Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 months ago
Arthur Silva Sens	ca18f298e1	Merge pull request #14949 from Maniktherana/minor-fixes-ct refac: make typeRequiresCT private	2 months ago
Bryan Boreham	9215252221	[BUGFIX] TSDB: Only query chunks up to truncation time (#14948 ) If the query overlaps the range currently undergoing compaction, we should only fetch chunks up to that time. Need to store that min time in `HeadAndOOOIndexReader`. Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 months ago
Manik Rana	3fba6bcdfa	chore: remove unused code Signed-off-by: Manik Rana <manikrana54@gmail.com>	2 months ago
Manik Rana	315165e49d	refac: make typeRequiresCT private Signed-off-by: Manik Rana <manikrana54@gmail.com>	2 months ago
Bryan Boreham	f53a94b9bb	Merge pull request #14920 from prometheus/prep-rel-2.55.0-rc.0 Prepare release 2.55.0-rc.0	2 months ago
Björn Rabenstein	5b9148e552	Merge pull request #14820 from charleskorn/promqltest-native-histogram-format promqltest: use test expression format for histograms in assertion failure messages and include reset hint in the test expression	2 months ago
Julien	146b22d196	fix(autoreload): Reload invalid yaml files When a YAML file is invalid, trigger auto-reload anyway so that user is aware that the configuration file is incorrect. Failing to do so does not change the reload status in metrics and api. Signed-off-by: Julien <roidelapluie@o11y.eu>	2 months ago
Julien	7ebda924b8	fix(web): properly format sub-millisecond durations in target status page Previously, scrapes durations that are very short (e.g., connection refused) could show as empty (durations under 1 millisecond). This commit ensures that sub-millisecond durations are correctly displayed as "0ms" or "1ms" when necessary. - Adjusted `humanizeDuration` to round sub-millisecond durations to the nearest millisecond. - Updated unit tests to verify the correct handling of sub-millisecond values. Signed-off-by: Julien <roidelapluie@o11y.eu>	2 months ago
Julien	5096bb9f29	Mantine UI: removed unuse file Signed-off-by: Julien <roidelapluie@o11y.eu>	2 months ago
Charles Korn	6dbb4e1a94	Fix linting issues Signed-off-by: Charles Korn <charles.korn@grafana.com>	2 months ago
Callum Styan	005bd33fe2	support v2 proto for BenchmarkSampleSend (#14935 ) Signed-off-by: Callum Styan <callumstyan@gmail.com>	2 months ago
Julius Volz	e480cf21eb	Merge pull request #14931 from prometheus/nexucis/autocomplete-topl UI/PromQL: autocomplete topk like aggregation function parameters	2 months ago
Björn Rabenstein	df9916ef66	Merge pull request #14677 from prometheus/beorn7/histogram promql(native histograms): Introduce exponential interpolation	2 months ago
Björn Rabenstein	c7fb6188b4	Merge pull request #14930 from jan--f/holt-winters-experimental move holt_winters to the experimental functions and rename	2 months ago
Augustin Husson	6e899fbb16	fix autocompletion when using by/without Signed-off-by: Augustin Husson <husson.augustin@gmail.com>	2 months ago
Jan Fajerski	aa6dd70812	changelog: record holt_winters rename Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	2 months ago
Jan Fajerski	96e5a94d29	promql: rename holt_winters to double_exponential_smoothing Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	2 months ago
Bryan Boreham	06022a6509	CHANGELOG: Add #14821 Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 months ago
Björn Rabenstein	1639450172	Merge pull request #14821 from charleskorn/nh-negative-multiplication-division promql: correctly handle unary negation of native histograms and add tests for multiplication and division of native histograms by negative scalars Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 months ago
Bryan Boreham	85cc1e941d	Merge pull request #14939 from prometheus/redo-14934 [release-2.55] TSDB: Backward compatibility with upcoming index v3	2 months ago
beorn7	6fcd225aee	promql(native histograms): Introduce exponential interpolation The linear interpolation (assuming that observations are uniformly distributed within a bucket) is a solid and simple assumption in lack of any other information. However, the exponential bucketing used by standard schemas of native histograms has been chosen to cover the whole range of observations in a way that bucket populations are spread out over buckets in a reasonably way for typical distributions encountered in real-world scenarios. This is the origin of the idea implemented here: If we divide a given bucket into two (or more) smaller exponential buckets, we "most naturally" expect that the samples in the original buckets will split among those smaller buckets in a more or less uniform fashion. With this assumption, we end up with an "exponential interpolation", which therefore appears to be a better match for histograms with exponential bucketing. This commit leaves the linear interpolation in place for NHCB, but changes the interpolation for exponential native histograms to exponential. This affects `histogram_quantile` and `histogram_fraction` (because the latter is more or less the inverse of the former). The zero bucket has to be treated specially because the assumption above would lead to an "interpolation to zero" (the bucket density approaches infinity around zero, and with the postulated uniform usage of buckets, we would end up with an estimate of zero for all quantiles ending up in the zero bucket). We simply fall back to linear interpolation within the zero bucket. At the same time, this commit makes the call to stick with the assumption that the zero bucket only contains positive observations for native histograms without negative buckets (and vice versa). (This is an assumption relevant for interpolation. It is a mostly academic point, as the zero bucket is supposed to be very small anyway. However, in cases where it _is_ relevantly broad, the assumption helps a lot in practice.) This commit also updates and completes the documentation to match both details about interpolation. As a more high level note: The approach here attempts to strike a balance between a more simplistic approach without any assumption, and a more involved approach with more sophisticated assumptions. I will shortly describe both for reference: The "zero assumption" approach would be to not interpolate at all, but _always_ return the harmonic mean of the bucket boundaries of the bucket the quantile ends up in. This has the advantage of minimizing the maximum possible relative error of the quantile estimation. (Depending on the exact definition of the relative error of an estimation, there is also an argument to return the arithmetic mean of the bucket boundaries.) While limiting the maximum possible relative error is a good property, this approach would throw away the information if a quantile is closer to the upper or lower end of the population within a bucket. This can be valuable trending information in a dashboard. With any kind of interpolation, the maximum possible error of a quantile estimation increases to the full width of a bucket (i.e. it more than doubles for the harmonic mean approach, and precisely doubles for the arithmetic mean approach). However, in return the _expectation value_ of the error decreases. The increase of the theoretical maximum only has practical relevance for pathologic distributions. For example, if there are thousand observations within a bucket, they could _all_ be at the upper bound of the bucket. If the quantile calculation picks the 1st observation in the bucket as the relevant one, an interpolation will yield a value close to the lower bucket boundary, while the true quantile value is close to the upper boundary. The "fancy interpolation" approach would be one that analyses the _actual_ distribution of samples in the histogram. A lot of statistics could be applied based on the information we have available in the histogram. This would include the population of neighboring (or even all) buckets in the histogram. In general, the resolution of a native histogram should be quite high, and therefore, those "fancy" approaches would increase the computational cost quite a bit with very little practical benefits (i.e. just tiny corrections of the estimated quantile value). The results are also much harder to reason with. Signed-off-by: beorn7 <beorn@grafana.com>	2 months ago
Bryan Boreham	81b9407f15	Prepare release 2.55.0-rc.0 Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 months ago
Julius Volz	c36589a6dd	Merge pull request #14940 from roidelapluie/subsecondzoom UI: Disallow sub-second zoom as this cause inconsistenices in the X axis in uPlot	2 months ago
Julien	546f780006	UI: Disallow sub-second zoom as this cause inconsistenices in the X axis in uPlot Fixes #9135 Signed-off-by: Julien <roidelapluie@o11y.eu>	2 months ago
Ganesh Vernekar	5ccb069414	Backward compatibility with upcoming index v3 Signed-off-by: Ganesh Vernekar <ganeshvern@gmail.com>	2 months ago

1 2 3 4 5 ...

14038 Commits (5710ddf24fd9a15710b391400aae4e4cc426e97a) All Branches Search

14038 Commits (5710ddf24fd9a15710b391400aae4e4cc426e97a)

All Branches