prometheus

Commit Graph

Author	SHA1	Message	Date
Kateryna Pavlova	d6e43b89f4	docs: add regex section in querying basics Signed-off-by: Kateryna Pavlova <kathrinett@gmail.com>	2 years ago
Kateryna Pavlova	bc008f1b0e	docs: fix range queries link Signed-off-by: Kateryna Pavlova <kathrinett@gmail.com>	2 years ago
Ben Kochie	869addfec8	Enable auto-gomaxprocs by default (#15378 ) Enable the `auto-gomaxprocs` feature flag by default. * Add command line flag `--no-auto-gomaxprocs` to disable. Signed-off-by: SuperQ <superq@gmail.com>	2 years ago
Ben Kochie	0f0deb77a2	Enable auto-gomemlimit by default (#15372 ) Enable the `auto-gomemlimit` feature flag by default. * Add command line flag `--no-auto-gomemlimit` to disable. Signed-off-by: SuperQ <superq@gmail.com>	2 years ago
gopi	372b83d7b8	Documented that WAL can still be written after memory-snapshot-on-shutdown (#15179 ) Documented that WAL can still be written after memory-snapshot-on-shutdown - #10824 Co-authored-by: Björn Rabenstein <github@rabenste.in> Signed-off-by: gopi <gopi.singaravelan.k@gmail.com> --------- Signed-off-by: Gopi-eng2202 <gopi.singaravelan.k@gmail.com> Signed-off-by: gopi <gopi.singaravelan.k@gmail.com> Co-authored-by: Björn Rabenstein <github@rabenste.in>	2 years ago
Jan Fajerski	f131cdd4c5	3.0 migration guide (#15099 ) * docs: 2 to 3 migration guide Signed-off-by: Jan Fajerski <jfajersk@redhat.com> * docs/stability: add 3.0 section Signed-off-by: Jan Fajerski <jfajersk@redhat.com> * docs/migration: details on enabling legacy name validation Signed-off-by: Owen Williams <owen.williams@grafana.com>\ * migration: add log format and `le` normalization Signed-off-by: Jan Fajerski <jfajersk@redhat.com> * migration: add new enable_http2 default for remote write Signed-off-by: Jan Fajerski <jfajersk@redhat.com> --------- Signed-off-by: Jan Fajerski <jfajersk@redhat.com> Signed-off-by: Owen Williams <owen.williams@grafana.com> Co-authored-by: Owen Williams <owen.williams@grafana.com>	2 years ago
Bryan Boreham	20fdc8f541	[CHANGE] Remote-write: default enable_http2 to false Remote-write creates several shards to parallelise sending, each with its own http connection. We do not want them all combined onto one socket by http2. Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	2 years ago
Jesus Vazquez	3cb09acb21	Docs: Remove experimental note on out of order feature (#15215 ) Signed-off-by: Jesus Vazquez <jesusvzpg@gmail.com>	2 years ago
Jonathan Ballet	7ca90e5729	doc: fix formatting Signed-off-by: Jonathan Ballet <jon@multani.info>	2 years ago
George Krajcsovits	1b4e7f74e6	feat(tools): add debug printouts to rules unit testing (#15196 ) * promtool: Add debug flag for rule tests This makes it print out the tsdb state (both input_series and rules that are run) at the end of a test, making reasoning about tests much easier. Signed-off-by: David Leadbeater <dgl@dgl.cx> * Reuse generated test name from junit testing Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com> --------- Signed-off-by: David Leadbeater <dgl@dgl.cx> Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com> Co-authored-by: David Leadbeater <dgl@dgl.cx>	2 years ago
alexgreenbank	3afcda82be	docs: add keep_firing_for in alerting rules Signed-off-by: alexgreenbank <alex.greenbank@grafana.com>	2 years ago
Yijie Qin	d2802c6fac	api: Add rule group pagination to list rules api (#14017 ) * Add paginated feature to list rules api Signed-off-by: Yijie Qin <qinyijie@amazon.com> * Refactor to simplify code: * Reduce number of variables * Reduce type convesion Signed-off-by: Raphael Silva <rapphil@gmail.com> * Simplify paginated implementation * Remove maxAlerts parameter. * Reuse existing API responses by using omitempty in some fields Signed-off-by: Raphael Silva <rapphil@gmail.com> * Simplify pagination implementation * Eliminate the need to sort the rule groups. Signed-off-by: Raphael Silva <rapphil@gmail.com> * Fix linting error Signed-off-by: Raphael Silva <rapphil@gmail.com> * Add more unit tests Signed-off-by: Raphael Silva <rapphil@gmail.com> * Update pagination parameters to be consistent with existing parameters Signed-off-by: Raphael Silva <rapphil@gmail.com> * Rename max_rule_groups to max_groups Signed-off-by: Raphael Silva <rapphil@gmail.com> * Refactor to simplify code Signed-off-by: Raphael Silva <rapphil@gmail.com> * Refactor to simplify the calculation of next token Signed-off-by: Raphael Silva <rapphil@gmail.com> * Handle corner case in pagination request Signed-off-by: Raphael Silva <rapphil@gmail.com> * Handle corner cases for pagination of list rules Signed-off-by: Raphael Silva <rapphil@gmail.com> * Update documentation for list rules parameters Signed-off-by: Raphael Silva <rapphil@gmail.com> * Refactor comments Signed-off-by: Raphael Silva <rapphil@gmail.com> * Simplify pagination implementation * Eliminate need for extra structs to store pagination parameters Signed-off-by: Raphael Silva <rapphil@gmail.com> * Update docs/querying/api.md Co-authored-by: Julius Volz <julius.volz@gmail.com> Signed-off-by: Raphael Philipe Mendes da Silva <rapphil@gmail.com> * Update web/api/v1/api.go Co-authored-by: Bartlomiej Plotka <bwplotka@gmail.com> Signed-off-by: Raphael Philipe Mendes da Silva <rapphil@gmail.com> * Update comment describing the need for next token Signed-off-by: Raphael Silva <rapphil@gmail.com> --------- Signed-off-by: Yijie Qin <qinyijie@amazon.com> Signed-off-by: Raphael Silva <rapphil@gmail.com> Signed-off-by: Raphael Philipe Mendes da Silva <rapphil@gmail.com> Co-authored-by: Raphael Silva <rapphil@gmail.com> Co-authored-by: Julius Volz <julius.volz@gmail.com> Co-authored-by: Bartlomiej Plotka <bwplotka@gmail.com>	2 years ago
machine424	8bcb4d865d	feat: normalize "le" and "quantile" labels values upon ingestion Signed-off-by: machine424 <ayoubmrini424@gmail.com> Co-authored-by: beorn7 <beorn@grafana.com>	2 years ago
Alex Greenbank	421a3c22ea	scrape: provide a fallback format (#15136 ) scrape: Remove implicit fallback to the Prometheus text format Remove implicit fallback to the Prometheus text format in case of invalid/missing Content-Type and fail the scrape instead. Add ability to specify a `fallback_scrape_protocol` in the scrape config. --------- Signed-off-by: alexgreenbank <alex.greenbank@grafana.com> Signed-off-by: Alex Greenbank <alex.greenbank@grafana.com> Co-authored-by: Björn Rabenstein <beorn@grafana.com>	2 years ago
Bartlomiej Plotka	efc43d0714	s/scrape_classic_histograms/always_scrape_classic_histograms (3.0 breaking change) (#15178 ) This is for readability, especially when we can converting to nhcb option. See discussion https://cloud-native.slack.com/archives/C077Z4V13AM/p1729155873397889 Signed-off-by: bwplotka <bwplotka@gmail.com>	2 years ago
Yi	2cabd1b707	config: remove expand-external-labels flag in release 3.0 (#14657 ) remove expand-external-labels feature flag and enabled env arg expansion for external labels by default. Signed-off-by: jyz0309 <45495947@qq.com>	2 years ago
Arve Knudsen	de16f5e387	[FEATURE] PromQL: Add experimental info function MVP (#14495 ) The `info` function is an experiment to improve UX around including labels from info metrics. `info` has to be enabled via the feature flag `--enable-feature=promql-experimental-functions`. This MVP of info simplifies the implementation by assuming: * Only support for the target_info metric * That target_info's identifying labels are job and instance Also: * Encode info samples' original timestamp as sample value * Deduce info series select hints from top-most VectorSelector --------- Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com> Co-authored-by: Ying WANG <ying.wang@grafana.com> Co-authored-by: Augustin Husson <augustin.husson@amadeus.com> Co-authored-by: Bartlomiej Plotka <bwplotka@gmail.com> Co-authored-by: Björn Rabenstein <github@rabenste.in> Co-authored-by: Bryan Boreham <bjboreham@gmail.com>	2 years ago
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>	2 years ago
Julien	7eb73b10d8	Remove http client config from consul and digitalocean Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	57e3fd0c51	Remove http options from docker and dockerswarm sd Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	5f13098403	Remove http client config from EC2 and PuppetDB Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	409d924381	Remove client HTTP settings from HTTP SD and Hetzner SD Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	62b26ac13c	Remove HTTP config docs from Kuma, Kubernetes and IONOS Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	04b12014a6	Remove http client docs from linode and lightsail Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	530c3fc345	Remove HTTP client doc from nomad and marathon Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	1dd45fd286	Remove http options from Eureka and Scaleway Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	aef84c068b	Remove http options from uyuni Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	675349c849	Remove HTTP options from vultr Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	6acf2dc054	Remove HTTP options from alerting Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Julien	e7206c2630	Remove http options from remote read/write Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years 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>	2 years 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>	2 years ago
Julien	db730fcade	Document the notifications API Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years ago
Jan Fajerski	563bfdd384	storage: require selectors to always return matching results Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	2 years 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>	2 years 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>	2 years ago
Julien	f9bbad1148	Limit the number of SSE Subscribers to 16 by default Signed-off-by: Julien <roidelapluie@o11y.eu>	2 years 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 years ago
Alex Johnson	be0f10054e	Remove no-default-scrape-port featureFlag Signed-off-by: Alex Johnson <alex.kattathra.johnson@gmail.com>	2 years 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 years ago
Jan Fajerski	96e5a94d29	promql: rename holt_winters to double_exponential_smoothing Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	2 years 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 years ago
Jan Fajerski	15cea39136	promql: put holt_winters behind experimental feature flag Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	2 years ago
Nihal	d0d57ff642	[DOC] Add username_file in basic auth http client config (#12749 ) Signed-off-by: Wasim Nihal <sswasim64@gmail.com>	2 years ago
Augustin Husson	6febfbb3be	put back feature flag 'delayed-compaction' and 'old-ui' (#14909 ) Signed-off-by: Augustin Husson <husson.augustin@gmail.com>	2 years ago
Jan Fajerski	722f33225c	docs/feature_flags.md: drop `agent` feature flag Signed-off-by: Jan Fajerski <jfajersk@redhat.com>	2 years ago
Nathan Baulch	50cd453c8f	chore: Fix typos (#14868 ) * Fix typos --------- Signed-off-by: Nathan Baulch <nathan.baulch@gmail.com>	2 years ago
Julius Volz	f1e0939f2f	Document /api/v1/parse_expr endpoint Signed-off-by: Julius Volz <julius.volz@gmail.com>	2 years 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>	2 years 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>	2 years ago

1 2 3 4 5 ...

898 Commits (d6e43b89f45c0540d6cd4743ffeaa0feb69e65ad)