PR to demonstrate the 30 commits introduced by Us #14

…ules/github.com/scaleway/scaleway-sdk-go-1.0.0-beta.30 Bump github.com/scaleway/scaleway-sdk-go from 1.0.0-beta.29 to 1.0.0-beta.30

…ules/golang.org/x/oauth2-0.23.0 Bump golang.org/x/oauth2 from 0.22.0 to 0.23.0

…ules/golang.org/x/tools-0.24.0 Bump golang.org/x/tools from 0.23.0 to 0.24.0

…ules/github.com/prometheus/common-0.59.0 Bump github.com/prometheus/common from 0.58.0 to 0.59.0

…ules/documentation/examples/remote_storage/github.com/prometheus/client_golang-1.20.2 Bump github.com/prometheus/client_golang from 1.19.1 to 1.20.2 in /documentation/examples/remote_storage

Bumps [github.com/prometheus/exporter-toolkit](https://github.com/prometheus/exporter-toolkit) from 0.11.0 to 0.12.0. - [Release notes](https://github.com/prometheus/exporter-toolkit/releases) - [Changelog](https://github.com/prometheus/exporter-toolkit/blob/master/CHANGELOG.md) - [Commits](prometheus/exporter-toolkit@v0.11.0...v0.12.0) --- updated-dependencies: - dependency-name: github.com/prometheus/exporter-toolkit dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>

Bumps [github.com/digitalocean/godo](https://github.com/digitalocean/godo) from 1.121.0 to 1.122.0. - [Release notes](https://github.com/digitalocean/godo/releases) - [Changelog](https://github.com/digitalocean/godo/blob/main/CHANGELOG.md) - [Commits](digitalocean/godo@v1.121.0...v1.122.0) --- updated-dependencies: - dependency-name: github.com/digitalocean/godo dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>

Bumps [golang.org/x/text](https://github.com/golang/text) from 0.17.0 to 0.18.0. - [Release notes](https://github.com/golang/text/releases) - [Commits](golang/text@v0.17.0...v0.18.0) --- updated-dependencies: - dependency-name: golang.org/x/text dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>

…logger Add support for logging scrape failures to a specified file

Target parameter labels should not be overridden by config params

…ules/github.com/prometheus/exporter-toolkit-0.12.0 Bump github.com/prometheus/exporter-toolkit from 0.11.0 to 0.12.0

Bumps [github.com/prometheus/common](https://github.com/prometheus/common) from 0.58.0 to 0.59.1. - [Release notes](https://github.com/prometheus/common/releases) - [Changelog](https://github.com/prometheus/common/blob/main/RELEASE.md) - [Commits](prometheus/common@v0.58.0...v0.59.1) --- updated-dependencies: - dependency-name: github.com/prometheus/common dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>

…ules/github.com/prometheus/common-0.59.1 Bump github.com/prometheus/common from 0.58.0 to 0.59.1

…ules/github.com/digitalocean/godo-1.122.0 Bump github.com/digitalocean/godo from 1.121.0 to 1.122.0

…ules/go-opentelemetry-io-14eb93439b Bump the go-opentelemetry-io group across 1 directory with 6 updates

…ules/golang.org/x/text-0.18.0 Bump golang.org/x/text from 0.17.0 to 0.18.0

…ules/github.com/linode/linodego-1.40.0 Bump github.com/linode/linodego from 1.38.0 to 1.40.0

Bumps [github.com/docker/docker](https://github.com/docker/docker) from 27.1.1+incompatible to 27.2.0+incompatible. - [Release notes](https://github.com/docker/docker/releases) - [Commits](moby/moby@v27.1.1...v27.2.0) --- updated-dependencies: - dependency-name: github.com/docker/docker dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>

Bumps [github.com/miekg/dns](https://github.com/miekg/dns) from 1.1.61 to 1.1.62. - [Changelog](https://github.com/miekg/dns/blob/master/Makefile.release) - [Commits](miekg/dns@v1.1.61...v1.1.62) --- updated-dependencies: - dependency-name: github.com/miekg/dns dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>

…ules/github.com/miekg/dns-1.1.62 Bump github.com/miekg/dns from 1.1.61 to 1.1.62

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 <[email protected]>

…#14848) * Update storage.md with the latest around Remote Write 2.0 Signed-off-by: Bartlomiej Plotka <[email protected]> * Update storage.md Signed-off-by: Bartlomiej Plotka <[email protected]> --------- Signed-off-by: Bartlomiej Plotka <[email protected]>

Signed-off-by: Julien <[email protected]>

…ules/k8s-io-a0fc09b0c0 Bump the k8s-io group across 1 directory with 3 updates

utf8: enable utf-8 support by default

…ules/github.com/docker/docker-27.2.0incompatible Bump github.com/docker/docker from 27.1.1+incompatible to 27.2.0+incompatible

Bumps [github.com/go-zookeeper/zk](https://github.com/go-zookeeper/zk) from 1.0.3 to 1.0.4. - [Release notes](https://github.com/go-zookeeper/zk/releases) - [Commits](go-zookeeper/zk@v1.0.3...v1.0.4) --- updated-dependencies: - dependency-name: github.com/go-zookeeper/zk dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

… config Signed-off-by: Julius Volz <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

Signed-off-by: Arve Knudsen <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

…heus#14612) * OTLP: Support context cancellation/timeout during translation --------- Signed-off-by: Arve Knudsen <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

* Limit memory usage Go tests with race detector Preliminary fix for prometheus#14858 Signed-off-by: Julius Volz <[email protected]> * Use CI job env var instead for Go memory limits Signed-off-by: Julius Volz <[email protected]> --------- Signed-off-by: Julius Volz <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

Signed-off-by: Charles Korn <[email protected]>

…pported Signed-off-by: Charles Korn <[email protected]>

Signed-off-by: Charles Korn <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

…plain Signed-off-by: Julius Volz <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

Merge new UI branch for Prometheus 3.0 into main

Followup to prometheus#14831 Signed-off-by: György Krajcsovits <[email protected]>

Signed-off-by: György Krajcsovits <[email protected]>

Signed-off-by: Julien <[email protected]>

…ery2

…uery2 BUGFIX: TSDB: panic in chunk querier

[Comment] Correct the comment on Decbuf.UvarintBytes

Seems to at least make more sense to me like that. Signed-off-by: Julius Volz <[email protected]>

…ntry Move AM discovery page from "Monitoring status" -> "Server status"

Conflicts: cmd/prometheus/main.go docs/command-line/prometheus.md docs/feature_flags.md web/ui/build_ui.sh web/web.go Resolved by dropping the UTF-8 feature flag and adding the `auto-reload-config` feature flag. For the new web ui pick all changes from `main`.

Scrape: test for q-value compliance with RFC 9110 in Accept header

Signed-off-by: Jan Fajerski <[email protected]>

Signed-off-by: Robert Fratto <[email protected]>

Signed-off-by: Jan Fajerski <[email protected]>

IMO this looks nicer than adding it as a normal page nav link as in prometheus#14878 Signed-off-by: Julius Volz <[email protected]>

Signed-off-by: Nicolás Pazos <[email protected]>

3.0 main sync 24 09 09

Pick up new promci action to automatically configure `GOMEMLIMIT`. Signed-off-by: SuperQ <[email protected]>

Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 22.5.2 to 22.5.4. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Fixes prometheus#14859, although we'll have to see about a long-term fix. Hopefully it'll be fixed upstream with a follow-up version. Signed-off-by: Julius Volz <[email protected]>

…ainer remove rfratto as a tsdb/agent maintainer

Signed-off-by: Fiona Liao <[email protected]>

Signed-off-by: Fiona Liao <[email protected]> Co-authored-by: Owen Williams <[email protected]>

Signed-off-by: Fiona Liao <[email protected]>

This reverts commit e1c2c51. Signed-off-by: Fiona Liao <[email protected]>

Signed-off-by: Julien <[email protected]>

…alertmanagers Mantine UI: Fix 404 on /discovered-alertmanagers

Bring back documentation link in the form of an action button

Signed-off-by: Julien <[email protected]>

Signed-off-by: Fiona Liao <[email protected]>

Mantine UI: Use actual lookback delta in explain

fix(utf8): propagate validationScheme config to scraping options

Signed-off-by: Julien <[email protected]>

…iplication-division promql: correctly handle unary negation of native histograms and add tests for multiplication and division of native histograms by negative scalars

…mci_2 Update promci action

Signed-off-by: Jan Fajerski <[email protected]>

Signed-off-by: Julien <[email protected]>

Explain: Use param scalars in aggregations description

Follow-up to prometheus#14893 Signed-off-by: Julius Volz <[email protected]>

test: pass enable_npm to setup_environment

Co-authored-by: Julien <[email protected]> Signed-off-by: Fiona Liao <[email protected]>

Signed-off-by: Fiona Liao <[email protected]>

…xplain Fix HTML rendering for aggregator Explain view

Signed-off-by: Fiona Liao <[email protected]>

Prepare release 3.0.0-beta.0

Conflicts: scrape/scrape_test.go Pick both changes.

Cut release 3.0 beta.0

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4.3.4 to 4.4.0. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@0b2256b...5076954) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Fix typos --------- Signed-off-by: Nathan Baulch <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

Signed-off-by: Sandro <[email protected]>

…rometheus#14897) Signed-off-by: Arve Knudsen <[email protected]>

…theus#14850) * tsdb: mmapCurrentOOOHeadChunk prepare for multiple ooo chunks Currently float samples can only create a single ooo head chunk, but native histograms can result in multiple due to counter resets, etc. Signed-off-by: György Krajcsovits <[email protected]> * tsdb: getOOOSeriesChunks prepare for multiple ooo chunks Currently float samples can only create a single ooo head chunk, but native histograms can result in multiple due to counter resets, etc. Signed-off-by: György Krajcsovits <[email protected]> --------- Signed-off-by: György Krajcsovits <[email protected]>

…provided This commit introduces the ability to skip the UI build in the Makefile by providing prebuilt UI assets, addressing the needs of users who may not have npm installed or who do not want to go through the front-end build process. To achieve this, we added the `PREBUILT_ASSETS_STATIC_DIR` environment variable. If this variable is set, the Makefile will skip the UI build and related tasks, such as bundling npm licenses. Instead, it will use the prebuilt assets from the specified directory. We already publish prebuilt UI assets as part of our release artifacts (e.g., `prometheus-web-ui-3.0.0-beta.0.tar.gz`). Users can download this tarball, extract it, and point the `PREBUILT_ASSETS_STATIC_DIR` to the extracted folder. This reduces build complexity, especially for users who don't have a development environment for front-end builds. For example, you can use the command: `make PREBUILT_ASSETS_STATIC_DIR=static build` where `static` refers to the directory containing the prebuilt UI files. This change simplifies the build process while still allowing users to use a prebuilt UI if desired. This solution is particularly useful for users who don't need to modify the UI and prefer to use the prebuilt version that we provide with each release. Signed-off-by: Julien <[email protected]>

ui: drop readme from template

…coloring Fix border color for target pools with one target that is failing

...initially fixing the ellipsis overflow text cut-off in badges. Signed-off-by: Julius Volz <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

Signed-off-by: Jan Fajerski <[email protected]>

docs/feature_flags.md: drop `agent` feature flag

In a non-dev build (no initial double-renders), the tree lines would not be rendered correctly from the parent of a binop to its first child, because the first child would be rendered before the parent, and the parent's ref hadn't been set yet at that time. Switched from a normal ref to a callback-based ref with explicit React state update to make sure that the child gets to know about the parent's (later) rendered div element. Signed-off-by: Julius Volz <[email protected]>

…rovements UI improvements: Factor out common styles, fix tree node line rendering, always show full badge contents (no ellipsis)

makefile: Add support for skipping UI build when prebuilt assets are provided

Set operators are not displayed: https://github.com/prometheus/prometheus/blob/31ce9dacf4a3714898e8620b09a753e16e2cf32a/web/ui/mantine-ui/src/pages/query/ExplainViews/BinaryExpr/VectorVector.tsx#L364 Therefore, do not compute results for them. Fixes prometheus#14889 Signed-off-by: Julien <[email protected]>

Explain, vector-to-vector: Do not compute results for set operators

…ules/github.com/go-zookeeper/zk-1.0.4 build(deps): bump github.com/go-zookeeper/zk from 1.0.3 to 1.0.4

…4909) Signed-off-by: Augustin Husson <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

Several regexps were coded like `"^.*$"`, which is an unnatural formulation nobody is likely to use. Inside `NewMatcher`, `^` and `$` are added anyway, which makes the form in the benchmark redundant. It even printed it out in the expected way. Signed-off-by: Bryan Boreham <[email protected]>

PromQL explain view: Support set operators

Signed-off-by: Julius Volz <[email protected]>

Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.5.4 to 5.6.2. - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release.yml) - [Commits](microsoft/TypeScript@v5.5.4...v5.6.2) --- updated-dependencies: - dependency-name: typescript dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>

* Add support for running govulncheck --------- Signed-off-by: 51n15t9r <[email protected]>

…rovements New UI: Better time formatting + tests, better styling

…rometheus#14849) * Change LabelQuerier.LabelValues() to return sorted values --------- Signed-off-by: 🌲 Harry 🌊 John 🏔 <[email protected]>

…les (prometheus#14546) Add support for ingesting OOO native histograms * Add flag for enabling and disabling OOO native histogram ingestion * Update OOO querying tests to include native histogram samples * Add OOO head tests * Add test for OOO native histogram counter reset headers Signed-off-by: Carrie Edwards <[email protected]> Signed-off-by: György Krajcsovits <[email protected]> Co-authored by: Carrie Edwards <[email protected]> Co-authored by: Jeanette Tan <[email protected]> Co-authored by: György Krajcsovits <[email protected]> Co-authored by: Fiona Liao <[email protected]>

…nchmark TSDB: Simplify benchmark regexps

…d_yarn/web/ui/typescript-5.6.2 Bump typescript from 5.5.4 to 5.6.2 in /web/ui

Shortcut for `.*` matches newlines as well. Add preamble change ^(?s: Add test dotAll flag por al regex Add and fix regex tests Signed-off-by: Mario Fernandez <[email protected]>

…silient Signed-off-by: machine424 <[email protected]>

…12749) Signed-off-by: Wasim Nihal <[email protected]>

Signed-off-by: Julien <[email protected]>

Signed-off-by: junya koyama <[email protected]>

…4854) fix(bstream/writeByte): ensure it appends only one byte Signed-off-by: Antoine Pultier <[email protected]>

build(deps): bump lru-cache from 7.18.3 to 11.0.1 in /web/ui

mantine UI: Distinguish between Not Ready and Stopping

…age (prometheus#14925) is reported for these benchmarks to more accurately reflect what's actually allocated Signed-off-by: Callum Styan <[email protected]>

…e_regex [CHANGE] regexp . to match \n and optimize performance

Signed-off-by: Augustin Husson <[email protected]>

* Make rate possible non-counter annotation consistent Previously a PossibleNonCounterInfo annotation would be left in cases where a range-vector selects 1 float data point, even if no more points are selected in order to calculate a rate. This change ensures an output float exists before emitting such an annotation. This fixes an inconsistency where a series with mixed data (ie, a float and a native histogram) would emit an annotation without any points. For example, ``` load 1m series{label="a"} 1 {{schema:1 sum:10 count:5 buckets:[1 2 3]}} eval instant at 1m rate(series[1m1s]) ``` Would have a PossibleNonCounterInfo annotation. Wheras ``` load 1m series{label="a"} {{schema:1 sum:10 count:5 buckets:[1 2 3]}} {{schema:1 sum:15 count:10 buckets:[1 2 3]}} eval instant at 1m rate(series[1m1s]) ``` Would not. --------- Signed-off-by: Joshua Hesketh <[email protected]>

Benchmarks must do the same work N times. Run 3 cases, where the values are constant, vary a bit, and vary a lot. Also aim for 120 samples same as TSDB default. Signed-off-by: Bryan Boreham <[email protected]>

Rather than append a zero then set the value at that position, append the value. Signed-off-by: Bryan Boreham <[email protected]>

Instead of a 2-bit write followed by a 14-bit write, do two 8-bit writes, which goes much faster since it avoids looping. Signed-off-by: Bryan Boreham <[email protected]>

Signed-off-by: Jan Fajerski <[email protected]>

Signed-off-by: Bryan Boreham <[email protected]>

…uery2 BUGFIX: TSDB: panic in chunk querier

Fixes prometheus#14859, although we'll have to see about a long-term fix. Hopefully it'll be fixed upstream with a follow-up version. Signed-off-by: Julius Volz <[email protected]>

Signed-off-by: Ganesh Vernekar <[email protected]>

…xis in uPlot Fixes prometheus#9135 Signed-off-by: Julien <[email protected]>

UI: Disallow sub-second zoom as this cause inconsistenices in the X axis in uPlot

Signed-off-by: Bryan Boreham <[email protected]>

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 <[email protected]>

[release-2.55] TSDB: Backward compatibility with upcoming index v3

…iplication-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 <[email protected]>

Signed-off-by: Bryan Boreham <[email protected]>

Signed-off-by: Jan Fajerski <[email protected]>

Signed-off-by: Augustin Husson <[email protected]>

…ntal move holt_winters to the experimental functions and rename

promql(native histograms): Introduce exponential interpolation

…ete-topl UI/PromQL: autocomplete topk like aggregation function parameters

Signed-off-by: Callum Styan <[email protected]>

Signed-off-by: Charles Korn <[email protected]>

Signed-off-by: Julien <[email protected]>

…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 <[email protected]>

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 <[email protected]>

…e-histogram-format promqltest: use test expression format for histograms in assertion failure messages and include reset hint in the test expression

Prepare release 2.55.0-rc.0

Signed-off-by: Manik Rana <[email protected]>

) 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 <[email protected]>

refac: make typeRequiresCT private

) 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 <[email protected]>

Also update the date of the RC which hasn't gone out yet. Signed-off-by: Bryan Boreham <[email protected]>

…ritebits [PERF] TSDB: Chunk encoding: shorten some write sequences

[release-2.55] Add prometheus#14948 to rc0

fix(web): properly format sub-millisecond durations in target status page

Mantine UI: removed unuse file

…hange chore: remove unused code

unsafe.Slice and unsafe.StringData were added in Go 1.20 Signed-off-by: Bryan Boreham <[email protected]>

Make text more consistent with 3.0 branch Signed-off-by: Bryan Boreham <[email protected]>

…to-main Signed-off-by: Bryan Boreham <[email protected]>

Signed-off-by: Bryan Boreham <[email protected]> prometheus#14402 is the issue and prometheus#14403 is the fix.

fix(autoreload): Reload invalid yaml files

Signed-off-by: György Krajcsovits <[email protected]>

cd web/ui/react-app npm install Signed-off-by: Arve Knudsen <[email protected]>

Merge 2.55 into main

@MichaHoffmann

…metheus#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 <[email protected]> * 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 <[email protected]> * Rename to evalVectorSelector Rename to evalVectorSelector after discussing with @MichaHoffmann. Signed-off-by: Arve Knudsen <[email protected]> --------- Signed-off-by: Arve Knudsen <[email protected]>

Optimize constant label pair adding from relabeling.

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 <[email protected]>

Signed-off-by: Jesus Vazquez <[email protected]>

docs: Improve, clarify, and fix documentation on scrape limits

…ui-assets-relative UI: Make mantime UI assets relative

We are still seeing lock contention on MemPostings.mtx, and MemPostings.Delete() is by far the most expensive operation on that mutex. This adds parallelism to that method, trying to reduce the amount of time we spend with the mutex held. Signed-off-by: Oleg Zaytsev <[email protected]>

[PERF] TSDB: Grow postings by doubling

Signed-off-by: Oleg Zaytsev <[email protected]>

Signed-off-by: Alex Johnson <[email protected]>

Signed-off-by: Julius Volz <[email protected]>

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 <[email protected]>

…staleness Docs: Refer to staleness in instant vector documentation

Signed-off-by: Oleg Zaytsev <[email protected]>

Signed-off-by: Arthur Silva Sens <[email protected]>

…theus#13909) * [ENHANCEMENT] Alerts: remove metrics for removed Alertmanagers So they don't continue to report stale values. Signed-off-by: Bryan Boreham <[email protected]>

Histogram CT Zero ingestion

…prometheus#14447) * scrape/scrape_test.go: reduce the time it takes to reload the manager TestNativeHistogramMaxSchemaSet took over 3x5s to complete because there's a minimum reload interval. I've made the testcases run in parallel and reduced the reload interval to 10ms. Now the test runs in around 0.1-0.2 seconds. Ran test 10000 times to check if it's flaky. Signed-off-by: György Krajcsovits <[email protected]> --------- Signed-off-by: György Krajcsovits <[email protected]>

…-13959 Remove no-default-scrape-port featureFlag

…t-alert-close-buttons Remove Query page alert close buttons that don't do anything

The pattern of `import _ "net/http/pprof"` adds handlers to the default http handler, but Prometheus does not use that. There are explicit handlers in `web/web.go`. So, we can remove this line with no impact to behaviour. Signed-off-by: Bryan Boreham <[email protected]>

Signed-off-by: Oleg Zaytsev <[email protected]>

This commit introduces a new `/api/v1/notifications/live` endpoint that utilizes Server-Sent Events (SSE) to stream notifications to the web UI. This is used to display alerts such as when a configuration reload has failed. I opted for SSE over WebSockets because SSE is simpler to implement and more robust for our use case. Since we only need one-way communication from the server to the client, SSE fits perfectly without the overhead of establishing and maintaining a two-way WebSocket connection. When the SSE connection fails, we go back to a classic /api/v1/notifications API endpoint. This commit also contains the required UI changes for the new Mantine UI. Signed-off-by: Julien <[email protected]>

Add notifications to the Web UI

Signed-off-by: Julien <[email protected]>

This switches from the prehistoric EventSource API to the more modern fetch-event-source package. That packages gives us full control over the retries. It also gives us the opportunity to close the event source when the browser tab is hidden, saving resources. Signed-off-by: Julien <[email protected]>

Signed-off-by: machine424 <[email protected]>

…elete-with-gomaxprocs-workers Process `MemPostings.Delete()` with `GOMAXPROCS` workers

Follow-up on notifications via SSE

…ling/marshalling is broken. This went under the radar because the utils are never called directly. We usually marshall/unmarshal Configs as embeded in a struct using UnmarshalYAMLWithInlineConfigs/MarshalYAMLWithInlineConfigs which bypasses Configs' custom UnmarshalYAML/MarshalYAML Signed-off-by: machine424 <[email protected]>

…UnmarshalYAML Signed-off-by: machine424 <[email protected]>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

PR to demonstrate the 30 commits introduced by Us #14

PR to demonstrate the 30 commits introduced by Us #14

Commits on Sep 6, 2024

Commits on Sep 7, 2024

Commits on Sep 8, 2024

Commits on Sep 9, 2024

Commits on Sep 10, 2024

Commits on Sep 11, 2024

Commits on Sep 12, 2024

Commits on Sep 13, 2024

Commits on Sep 14, 2024

Commits on Sep 16, 2024

Commits on Sep 17, 2024

Commits on Sep 18, 2024

Commits on Sep 19, 2024

Commits on Sep 20, 2024

Commits on Sep 21, 2024

Commits on Sep 22, 2024

Commits on Sep 23, 2024

Commits on Sep 24, 2024

Commits on Sep 25, 2024

Commits on Sep 26, 2024

Commits on Sep 27, 2024

Commits on Sep 29, 2024

Commits on Sep 30, 2024

PR to demonstrate the 30 commits introduced by Us #14

Are you sure you want to change the base?

PR to demonstrate the 30 commits introduced by Us #14

Commits on Sep 6, 2024

Commits on Sep 7, 2024

Commits on Sep 8, 2024

Commits on Sep 9, 2024

Commits on Sep 10, 2024

Commits on Sep 11, 2024

Commits on Sep 12, 2024

Commits on Sep 13, 2024

Commits on Sep 14, 2024

Commits on Sep 16, 2024

Commits on Sep 17, 2024

Commits on Sep 18, 2024

Commits on Sep 19, 2024

Commits on Sep 20, 2024

Commits on Sep 21, 2024

Commits on Sep 22, 2024

Commits on Sep 23, 2024

Commits on Sep 24, 2024

Commits on Sep 25, 2024

Commits on Sep 26, 2024

Commits on Sep 27, 2024

Commits on Sep 29, 2024

Commits on Sep 30, 2024