prometheus

Commit Graph

Author	SHA1	Message	Date
Charles Korn	0fbe5af961	Fix heading for `limitk` docs Signed-off-by: Charles Korn <charleskorn@users.noreply.github.com>	7 months ago
György Krajcsovits	c929578718	feat(nh): mark native histograms as stable in docs Fixes: #16572 Mark as stable means that breaking changes are only allowed together with major version release of Prometheus. Co-authored-by: Björn Rabenstein <beorn@grafana.com> Signed-off-by: George Krajcsovits <krajorama@users.noreply.github.com> Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>	7 months ago
Julius Volz	ae83804ab0	docs: Minor formatting/typo fixes in the HTTP API docs (#17339 ) Signed-off-by: Julius Volz <julius.volz@gmail.com>	7 months ago
Julius Volz	8b1bd7d6c3	ui: Allow viewing detailed relabeling steps for each discovered target This adds: * A `ScrapePoolConfig()` method to the scrape manager that allows getting the scrape config for a given pool. * An API endpoint at `/api/v1/targets/relabel_steps` that takes a pool name and a label set of a target and returns a detailed list of applied relabeling rules and their output for each step. * A "show relabeling" link/button for each target on the discovery page that shows the detailed flow of all relabeling rules (based on the API response) for that target. Note that this changes the JSON encoding of the relabeling rule config struct to output the original snake_case (instead of camelCase) field names, and before merging, we need to be sure that's ok :) See my comment about that at https://github.com/prometheus/prometheus/pull/15383#issuecomment-3405591487 Fixes https://github.com/prometheus/prometheus/issues/17283 Signed-off-by: Julius Volz <julius.volz@gmail.com>	8 months ago
beorn7	e94031abd2	docs: Clarify the handling of negative histograms Signed-off-by: beorn7 <beorn@grafana.com>	8 months ago
Bryan Boreham	a59f3e090b	[DOCS] API: Document the lookback_delta parameter Signed-off-by: Bryan Boreham <bjboreham@gmail.com>	8 months ago
Simon Pasquier	dde7d6ad37	doc: clarify start/end for label API endpoints (#17217 ) Because the label API endpoints read from the TSDB indexes, they can return information for series which are present in the index but have no samples in the queried interval. Add similar note for the series endpoint. Signed-off-by: Simon Pasquier <spasquie@redhat.com>	8 months ago
Aditya Tiwari	1c974108f3	docs: fix typos and formatting in querying functions and storage Signed-off-by: Aditya Tiwari <adityatiwari342005@gmail.com>	9 months ago
Daniel Gospodinow	562d13e930	docs: minor grammar improvements in `basics.md` (#17077 ) Corrected minor grammatical errors in the documentation. Signed-off-by: Daniel Gospodinow <danielgospodinow@gmail.com>	9 months ago
Craig Ringer	1ce84d8e2f	feat(promql): add first_over_time and ts_of_first_over_time Add a first_over_time function, and corresponding ts_of_first_over_time function. Both are behind the experimental functions feature flag. Signed-off-by: Craig Ringer <craig.ringer@enterprisedb.com>	9 months ago
beorn7	1071c82b42	docs: counter vs. gauge histogram behavior with `+`/`-` This mostly handles the cases mentioned in #16576. However, there are some related changes in here, too: - Some line formatting to avoid lines longer than 80 characters. - Establish in basics.md that histograms have a counter vs. gauge "flavor" that is also stored in the sample and not just by convention as for float samples. - Add the documentation of the unary minus, which was missing so far. This require a bit of restructuring. - Cleaned up a few references to "Prometheus" that should better refer to "PromQL" (and "Prometheus's query language" → "PromQL" etc.). I decided to not explain in all detail when and how PromQL detects an incompatible counter reset. The spec is linked from basics.md, so the minority that might be interested in this can still look it up. Signed-off-by: beorn7 <beorn@grafana.com>	10 months ago
Charles Korn	8397b738bf	docs: clarify docs for PromQL aggregation operators (#16837 ) Signed-off-by: Charles Korn <charles.korn@grafana.com>	11 months ago
sujal shah	4408a6bcaf	api: Create `/status/tsdb/blocks` endpoint. this endpoint serves blocks data to the client. Signed-off-by: sujal shah <sujalshah28092004@gmail.com>	11 months ago
Charles Korn	d19a9ab673	Remove other instances of "obvious" Signed-off-by: Charles Korn <charles.korn@grafana.com>	11 months ago
Charles Korn	1977452331	Address PR feedback: adjust docs to match current behaviour Signed-off-by: Charles Korn <charles.korn@grafana.com>	11 months ago
Charles Korn	665eb3d6cb	Address PR feedback: remove use of "obvious" Signed-off-by: Charles Korn <charles.korn@grafana.com>	11 months ago
Charles Korn	70df21a680	Address PR feedback: format Inf and NaN as monospace Signed-off-by: Charles Korn <charles.korn@grafana.com>	11 months ago
Charles Korn	9c6916f4f9	Address PR feedback: add blank lines before lists Signed-off-by: Charles Korn <charles.korn@grafana.com>	11 months ago
George Krajcsovits	5b7ff92d95	fix(promql): histogram_quantile and histogram_fraction NaN observed in native histogram (#16724 ) * fix(promql): histogram_quantile NaN observed in native histogram Fixes: #16578 See the issue for detailed explanation. When a histogram had only NaN observations and no normal observations, we returned 0 from the quantile, which is completely wrong. If there were normal observations but we went over them, we returned the upper bound of the existing buckets, however that contradicts expectations on histogram_fraction. Now we return NaN if the quantile is calculated to be over all normal observations, falling into NaNs (in a virtual +Inf bucket). We also return info level annotations if we see any NaN observations. The annotation calls out if we returned NaN or even if we took the virtual +Inf bucket into account. Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com> * fix(promql): histogram_fraction NaN observed in native histogram Fixes: #16580 According to the specification we should not take NaN observations into account when calculating the fraction. This commit fixes that and adds an info level annotation to let the user know about this. Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>	11 months ago
Julien Pivotto	c07950e5e9	docs: remote read: Mention buf.build Signed-off-by: Julien Pivotto <291750+roidelapluie@users.noreply.github.com>	11 months ago
Julien Pivotto	0fb698675c	docs: Direct link to remote read proto to the main branch Left over of the master->main branch rename. Signed-off-by: Julien Pivotto <291750+roidelapluie@users.noreply.github.com>	12 months ago
Michael Hoffmann	a5fa9431d8	promql: add ts_of_(max,min,last)_over_time functions This commit adds the ts_of_(max,min,last)_over_time functions behind the experimental feature flag. Signed-off-by: Michael Hoffmann <mhoffmann@cloudflare.com>	12 months ago
Charles Korn	5926159f2a	Clarify expected behaviour of `on(__name__)` See https://github.com/prometheus/prometheus/issues/16631 Signed-off-by: Charles Korn <charles.korn@grafana.com>	12 months ago
Charles Korn	0c6ef1b23c	Clarify behaviour of `bool` modifier Signed-off-by: Charles Korn <charles.korn@grafana.com>	12 months ago
Charles Korn	40bed6281e	Clarify behaviour of metric names with `bool` modifier Based on discussion in https://github.com/prometheus/prometheus/issues/15471 Signed-off-by: Charles Korn <charles.korn@grafana.com>	12 months ago
Charles Korn	1e794f7ef9	Break large paragraphs into smaller pieces Signed-off-by: Charles Korn <charles.korn@grafana.com>	12 months ago
Julius Volz	13564c03ef	Standardize doc page title handling See https://groups.google.com/g/prometheus-developers/c/cwL3cM66Em8 Signed-off-by: Julius Volz <julius.volz@gmail.com>	1 year ago
marcoderama	778d49bbfb	docs: fix typo in operators.md Signed-off-by: marcoderama <marcoderamagit@gmail.com>	1 year ago
Julius Volz	1b818b03d5	Clean up codeboxes and headings in docs The new docs site will have syntax highlighting, so this adds language tags to code boxes that are currently missing them. I didn't add `promql` as a language yet since the highlighter doesn't support it yet, plus a lot of the PromQL codeboxes in our docs aren't strictly valid PromQL, they are more like multiple expressions listed in the same code box on multiple lines. So I'm leaving that for sometime later. In the HTTP API page, I moved the curl examples from the JSON codeboxes to their own ones above the JSON output. I considered putting an "Output:" text between the curl + JSON output, but I think the way it currently looks without it is probably fine. I also fixed a number of headings which were at the wrong level relative to their nesting in the document. I also removed `go` as a language from the Go template language examples, because the Go template language isn't Go at all. I also adjusted the indent on one codebox to be more reasonable (2 spaces instead of 8). And then finally, my editor made a bunch of whitespace changes automatically, like removing trailing spaces. Signed-off-by: Julius Volz <julius.volz@gmail.com> Signed-off-by: Julius Volz <julius.volz@gmail.com>	1 year ago
Aman	26bddcf068	promql: histogram_stddev and histogram_stdvar should use arithmetic mean for custom buckets Signed-off-by: amanycodes <amanycodes@gmail.com>	1 year ago
Michael Hoffmann	d6d9f97bac	promql: histogram_fraction for bucket histograms (#16095 ) * promql: histogram_fraction for bucket histograms This PR extends the histogram_fraction function to also work with classic bucket histograms. This is beneficial because it allows expressions like sum(increase(my_bucket{le="0.5"}[10m]))/sum(increase(my_total[10m])) to be written without knowing the actual values of the "le" label, easing the transition to native histograms later on. It also feels natural since histogram_quantile also can deal with classic histograms. Signed-off-by: Michael Hoffmann <mhoffmann@cloudflare.com> * promql: histogram_fraction for bucket histograms * Add documentation and reduce code duplication * Fix a bug in linear interpolation between bucket boundaries * Add more PromQL tests Signed-off-by: Michael Hoffmann <mhoffmann@cloudflare.com> * Update docs/querying/functions.md Co-authored-by: Björn Rabenstein <github@rabenste.in> Signed-off-by: Michael Hoffmann <mhoffm@posteo.de> --------- Signed-off-by: Michael Hoffmann <mhoffmann@cloudflare.com> Signed-off-by: Michael Hoffmann <mhoffm@posteo.de> Co-authored-by: Björn Rabenstein <github@rabenste.in>	1 year ago
co63oc	0e4e5a71bd	Fix typos (#16076 ) Signed-off-by: co63oc <co63oc@users.noreply.github.com>	1 year ago
Julius Volz	4be2243f06	Include scrape pool name for dropped targets in /api/v1/targets This is needed so we can display dropped targets in the right scrape pool in the web interface even if they have a non-default job name. See also https://github.com/prometheus/prometheus/pull/16078 Fixes https://github.com/prometheus/prometheus/issues/16065 Signed-off-by: Julius Volz <julius.volz@gmail.com>	1 year ago
Charles Korn	2cfd402b3a	Clarify sorting behaviour of `topk` and `bottomk`. Signed-off-by: Charles Korn <charles.korn@grafana.com>	1 year ago
Charles Korn	acd74b02fb	Fix typo Signed-off-by: Charles Korn <charles.korn@grafana.com>	1 year ago
beorn7	993d4e71c9	docs: Update PromQL documentation to match the native histogram spec This is also meant to document the actual implementation, but see #13934 for the current state. This also improves and streamlines some parts of the documentation that are not strictly native histogram related, but are colocated with them. In particular, the section about aggregation operators got restructured quite a bit, including the removal of a quite verbose example for `limit_ratio` (which was just too long an this location and also a bit questionabl in its usefulness). Signed-off-by: beorn7 <beorn@grafana.com>	1 year ago
asymmetric	96f31e370b	doc: clarify `rate` values are averaged (#14045 ) * doc: clarify `rate` values are averaged Signed-off-by: asymmetric <101816+asymmetric@users.noreply.github.com> Co-authored-by: Björn Rabenstein <github@rabenste.in>	1 year ago
sh0rez	5303e515af	remote/otlp: convert delta to cumulative (#15165 ) What Adds support for OTLP delta temporality to the OTLP endpoint. This is done by calling the deltatocumulative processor from the OpenTelemetry collector during OTLP conversion. Why Delta conversion is a naturally stateful process, which requires careful request routing when operated inside a collector. Prometheus is already stateful and doing the conversion in-server reduces the operational burden on the ingest architecture by only having one stateful component. How deltatocumulative is a OTel collector component that works as follows: * pmetric.Metrics come from a receiver or in this case from the HTTP client * It operates as an in-place update loop: * for each sample, if not delta, leave unmodified * if delta, do: * state += sample, where state is the in-memory sum of all previous samples * sample = state, sample value is now cumulative * this is supported for sums (counters), gauges, histograms (old histograms) and exponential histograms (native histograms) If a series receives no new samples for 5m, its state is removed from memory Performance Delta performance is a stateful operation and the OTel code is not highly optimized yet, e.g. it locks the entire processor for each request. Nonetheless, care has been taken to mitigate those effects: delta conversion is behind a feature flag. If disabled, no conversion code is ever invoked if enabled, conversion is not invoked if request not actually contains delta samples. This leads to no measureable performance difference between default-cumulative to convert-cumulative (only cumulative, feature on/off) Signed-off-by: sh0rez <me@shorez.de>	1 year ago
Vandit Singh	6339989e25	web/api: Add a limit parameter to /query and /query_range (#15552 ) add limit param to query and rangeQuery --------- Signed-off-by: Vandit Singh <vanditsinghkv@gmail.com> Signed-off-by: Vandit Singh <107131545+Vandit1604@users.noreply.github.com> Co-authored-by: Björn Rabenstein <github@rabenste.in>	1 year ago
sujal shah	73a3438c1b	api: Add two new fields Node and ServerTime. This commit introduced two field in `/status` endpoint: - The node currently serving the request. - The current server time for debugging time drift issues. fixes #15394. Signed-off-by: sujal shah <sujalshah28092004@gmail.com>	1 year ago
Owen Williams	12577e3851	Add support for values unescaping on `/v1/label/:name/values` endpoint Signed-off-by: Owen Williams <owen.williams@grafana.com>	2 years ago
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
Jonathan Ballet	7ca90e5729	doc: fix formatting Signed-off-by: Jonathan Ballet <jon@multani.info>	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
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
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

1 2 3 4 5 ...

287 Commits (efdfb8fed626ebbcddeeb60ea9ba8b29c13dbdf2)