prometheus

Commit Graph

Author	SHA1	Message	Date
Viet Hung Nguyen	f0a9f62ce8	[DOCS] Querying basics: what can be graphed Put a scalar to query, it can be graphed. So the doc says "an expression that returns an instant vector is the only type which can be graphed." is not correct? And also, a query_range, which used for graph, always return a range vector <https://promlabs.com/blog/2020/06/18/the-anatomy-of-a-promql-query/#range-queries> , so it's confusing to read the above statement. Signed-off-by: Viet Hung Nguyen <hvn@familug.org>	1 year ago
Julien	7eb73b10d8	Remove http client config from consul and digitalocean Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	57e3fd0c51	Remove http options from docker and dockerswarm sd Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	5f13098403	Remove http client config from EC2 and PuppetDB Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	409d924381	Remove client HTTP settings from HTTP SD and Hetzner SD Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	62b26ac13c	Remove HTTP config docs from Kuma, Kubernetes and IONOS Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	04b12014a6	Remove http client docs from linode and lightsail Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	530c3fc345	Remove HTTP client doc from nomad and marathon Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	1dd45fd286	Remove http options from Eureka and Scaleway Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	aef84c068b	Remove http options from uyuni Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	675349c849	Remove HTTP options from vultr Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	6acf2dc054	Remove HTTP options from alerting Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	e7206c2630	Remove http options from remote read/write Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	261d7d75eb	docs: extract HTTP client option documentation from scrape config Extracted HTTP client options (e.g., authentication, proxy settings, TLS configuration, and custom headers) into a dedicated section for improved clarity and organization. This will centralize all HTTP-related options from prometheus/common in one place within the documentation. The remaining HTTP-related settings in sections (e.g. Service Discovery) will be moved in a follow-up PR to further unify the documentation structure. Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
beorn7	08d4b034da	docs: Declare "float literals are time durations" as stable This unifies the documentation of float literals and time durations and updates all references to the old definitions. Signed-off-by: beorn7 <beorn@grafana.com>	1 year ago
Julien	db730fcade	Document the notifications API Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Jan Fajerski	563bfdd384	storage: require selectors to always return matching results Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	1 year ago
Jesus Vazquez	77d3b3aff3	OTLP: Remove experimental word form OTLP receiver (#14894 ) The OTLP receiver can now considered stable. We've had it for longer than a year in main and has received constant improvements. Signed-off-by: Jesus Vazquez <jesusvzpg@gmail.com>	1 year ago
Bryan Boreham	6b247c50d2	Revert "Merge pull request #14769 from roidelapluie/autoreload" This reverts commit `50f5327f83`, reversing changes made to `eb4004c344`. Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	1 year ago
Julien	f9bbad1148	Limit the number of SSE Subscribers to 16 by default Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year 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>	1 year ago
Alex Johnson	be0f10054e	Remove no-default-scrape-port featureFlag Signed-off-by: Alex Johnson <alex.kattathra.johnson@gmail.com>	1 year 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>	1 year ago
Jan Fajerski	96e5a94d29	promql: rename holt_winters to double_exponential_smoothing Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	1 year 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>	1 year ago
Jan Fajerski	15cea39136	promql: put holt_winters behind experimental feature flag Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	1 year ago
Nihal	d0d57ff642	[DOC] Add username_file in basic auth http client config (#12749 ) Signed-off-by: Wasim Nihal <sswasim64@gmail.com>	1 year ago
Augustin Husson	6febfbb3be	put back feature flag 'delayed-compaction' and 'old-ui' (#14909 ) Signed-off-by: Augustin Husson <husson.augustin@gmail.com>	1 year ago
Jan Fajerski	722f33225c	docs/feature_flags.md: drop `agent` feature flag Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	1 year ago
Nathan Baulch	50cd453c8f	chore: Fix typos (#14868 ) * Fix typos --------- Signed-off-by: Nathan Baulch <nathan.baulch@gmail.com>	1 year ago
Julius Volz	f1e0939f2f	Document /api/v1/parse_expr endpoint Signed-off-by: Julius Volz <julius.volz@gmail.com>	1 year ago
Bartlomiej Plotka	edc83ed164	Update storage.md with the latest around Remote Write 2.0 (#14848 ) * Update storage.md with the latest around Remote Write 2.0 Signed-off-by: Bartlomiej Plotka <bwplotka@gmail.com> * Update storage.md Signed-off-by: Bartlomiej Plotka <bwplotka@gmail.com> --------- Signed-off-by: Bartlomiej Plotka <bwplotka@gmail.com>	1 year ago
Owen Williams	88bb05c3e8	utf8: enable utf-8 support by default This change causes Prometheus to allow all UTF-8 characters in metric and label names. This means that names that were previously invalid and would have been previously rejected will be allowed through. Signed-off-by: Owen Williams <owen.williams@grafana.com>	1 year ago
machine424	cc40b65ab4	fix(promtool): use the final database path for --sandbox-dir-root instead of the default value as it may be overridden add a regression test for that. Signed-off-by: machine424 <ayoubmrini424@gmail.com>	1 year ago
Julien	be3597c272	Update autoreload documentation: recommend writing files atomically (#14836 ) Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
machine424	d18fa62ae9	chore(discovery): enable new-service-discovery-manager by default and drop legacymanager package Signed-off-by: machine424 <ayoubmrini424@gmail.com>	1 year ago
Julien	ce0f09b125	Scrape: Add scrape_failure_log_file to log Scrape Failures Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julius Volz	c73c3e24d7	Default to serving new (Prometheus 3.0) UI Signed-off-by: Julius Volz <julius.volz@gmail.com>	1 year ago
Arthur Silva Sens	ca1f30bb6e	Promote Agent mode to it's own cmdline flag Signed-off-by: Arthur Silva Sens <arthursens2005@gmail.com>	1 year ago
Jan Fajerski	befcfadf78	Fix merge conflicts Fix call to newTestEngine(t) in promql/engine_test.go:3214. `agent` feature-flag it's own cmdline flag now. Remove `scrape.name-escaping-scheme` argument. Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	1 year ago
Julien	deabb30b20	Document custom HTTP headers and add tests Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Julien	1cd2d0498b	Support reload config automatically Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Arthur Silva Sens	60b9e9fc16	Promote Agent mode to it's own cmdline flag Signed-off-by: Arthur Silva Sens <arthursens2005@gmail.com>	1 year ago
Kevin Rawal	b0677263c3	Update basics.md fix broken URL for feature flags native histograms in querying prometheus documentation Signed-off-by: Kevin Rawal <84058124+kevinrawal@users.noreply.github.com>	1 year ago
Jorge Creixell	e9e3d64b7c	PromQL engine: Delay deletion of __name__ label to the end of the query evaluation (#14477 ) PromQL engine: Delay deletion of __name__ label to the end of the query evaluation - This change allows optionally preserving the `__name__` label via the `label_replace` and `label_join` functions, and helps prevent the dreaded "vector cannot contain metrics with the same labelset" error. - The implementation extends the `Series` and `Sample` structs with a boolean flag indicating whether the `__name__` label should be deleted at the end of the query evaluation. - The `label_replace` and `label_join` functions can still access the value of the `__name__` label, even if it has been previously marked for deletion. If `__name__` is used as target label, it won't be dropped at the end of the query evaluation. - Fixes https://github.com/prometheus/prometheus/issues/11397 - See https://github.com/jcreixell/prometheus/pull/2 for previous discussion, including the decision to create this PR and benchmark it before considering other alternatives (like refactoring `labels.Labels`). - See https://github.com/jcreixell/prometheus/pull/1 for an alternative implementation using a special label instead of boolean flags. - Note: a feature flag `promql-delayed-name-removal` has been added as it changes the behavior of some "weird" queries (see https://github.com/prometheus/prometheus/issues/11397#issuecomment-1451998792) Example (this always fails, as `__name__` is being dropped by `count_over_time`): ``` count_over_time({__name__!=""}[1m]) => Error executing query: vector cannot contain metrics with the same labelset ``` Before: ``` label_replace(count_over_time({__name__!=""}[1m]), "__name__", "count_$1", "__name__", "(.+)") => Error executing query: vector cannot contain metrics with the same labelset ``` After: ``` label_replace(count_over_time({__name__!=""}[1m]), "__name__", "count_$1", "__name__", "(.+)") => count_go_gc_cycles_automatic_gc_cycles_total{instance="localhost:9090", job="prometheus"} 1 count_go_gc_cycles_forced_gc_cycles_total{instance="localhost:9090", job="prometheus"} 1 ... ``` Signed-off-by: Jorge Creixell <jcreixell@gmail.com> --------- Signed-off-by: Jorge Creixell <jcreixell@gmail.com> Signed-off-by: Björn Rabenstein <github@rabenste.in>	1 year ago
Julien Pivotto	ed2e18d7de	Add documentation for custom headers. Signed-off-by: Julien Pivotto <roidelapluie@o11y.eu> Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
Suraj Patil	7757794bb3	[ENHANCEMENT] Promtool: Adding labels to time series while creating tsdb blocks (#14403 ) * feat: #14402 - Adding labels to time series while creating tsdb blocks Signed-off-by: Suraj Patil <patilsuraj767@gmail.com>	1 year ago
machine424	88cac6fb49	docs(configuration.md): clarify the explanations about some temp labels and format for better visibility. Signed-off-by: machine424 <ayoubmrini424@gmail.com>	1 year ago
Julien Pivotto	9b5e7623f4	Add support for multiple listening addresses Fixes #9105 Signed-off-by: Julien Pivotto <roidelapluie@o11y.eu> Signed-off-by: Julien <roidelapluie@o11y.eu>	1 year ago
ouyang1204@gmail.com	89dee48cc8	fix the issue of failing to match the first network when the container is reconnected to a new network Signed-off-by: ouyang1204@gmail.com <ouyang1204@gmail.com>	1 year ago

1 2 3 4 5 ...

1013 Commits (aa1d46a9da0f9710ca1528bef7623f1b4fb93f53)