From 37018708558bf567056988978e1cc1170f198dce Mon Sep 17 00:00:00 2001 From: f41gh7 Date: Fri, 8 May 2026 13:45:15 +0200 Subject: [PATCH] docs: update version to v1.143.0 Signed-off-by: f41gh7 --- docs/victoriametrics/Cluster-VictoriaMetrics.md | 4 ++-- docs/victoriametrics/integrations/prometheus.md | 2 +- docs/victoriametrics/vmalert.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/victoriametrics/Cluster-VictoriaMetrics.md b/docs/victoriametrics/Cluster-VictoriaMetrics.md index 26c8098f5b..0222be0e43 100644 --- a/docs/victoriametrics/Cluster-VictoriaMetrics.md +++ b/docs/victoriametrics/Cluster-VictoriaMetrics.md @@ -68,7 +68,7 @@ The UI allows exploring query results via graphs and tables. See more details ab ## Multitenancy VictoriaMetrics cluster supports multiple isolated tenants (aka namespaces). -Tenants are identified by `accountID` or `accountID:projectID` inside request URLs or HTTP headers{{% available_from "#" %}} +Tenants are identified by `accountID` or `accountID:projectID` inside request URLs or HTTP headers{{% available_from "v1.143.0" %}} for writes and reads. See [these docs](#url-format) for details. Some facts about tenants in VictoriaMetrics: @@ -97,7 +97,7 @@ See also multitenancy [via headers](#multitenancy-via-headers) and [via labels]( By default, VictoriaMetrics allows specifying `accountID` and `projectID` only in the request URL. -Set `--enableMultitenancyViaHeaders` {{% available_from "#" %}} command-line flag to support +Set `--enableMultitenancyViaHeaders` {{% available_from "v1.143.0" %}} command-line flag to support specifying `accountID` and `projectID` via HTTP headers `AccountID` and `ProjectID` respectively. This flag needs to be specified separately for vminserts and vmselects. diff --git a/docs/victoriametrics/integrations/prometheus.md b/docs/victoriametrics/integrations/prometheus.md index 86b037af38..c124afc713 100644 --- a/docs/victoriametrics/integrations/prometheus.md +++ b/docs/victoriametrics/integrations/prometheus.md @@ -71,7 +71,7 @@ which can be used as faster and less resource-hungry alternative to Prometheus. ## Native histograms -Prometheus [native histogram](https://prometheus.io/docs/specs/native_histograms/) is automatically converted{{% available_from "#" %}} +Prometheus [native histogram](https://prometheus.io/docs/specs/native_histograms/) is automatically converted{{% available_from "v1.143.0" %}} to [VictoriaMetrics histogram format](https://valyala.medium.com/improving-histogram-usability-for-prometheus-and-grafana-bc7e5df0e350) with `vmrange` labels during ingestion. > After conversion, a native histogram is transformed into classic histograms with `_count`, `_sum`, and `_bucket` series. These series can be queried using standard histogram functions such as `histogram_quantile()`. diff --git a/docs/victoriametrics/vmalert.md b/docs/victoriametrics/vmalert.md index 6563fa3c17..87c010e350 100644 --- a/docs/victoriametrics/vmalert.md +++ b/docs/victoriametrics/vmalert.md @@ -1145,7 +1145,7 @@ vmalert [web UI](https://docs.victoriametrics.com/victoriametrics/vmalert/#web), to them if this information is sensitive. Specifically: * Log messages, the UI, and exported metrics contain full path to the configured rule files. These file paths can be stripped - by enabling `-rule.stripFilePath` command-line flag {{% available_from "#" %}}; + by enabling `-rule.stripFilePath` command-line flag {{% available_from "v1.143.0" %}}; * Datasource address is sanitized in log messages, UI and exported metrics, can be shown by enabling ` -datasource.showURL`; * Notifier addresses are sanitized in log messages, UI and exported metrics, can be shown by enabling `-notifier.showURL`; * Remote read address is sanitized in log messages, UI and exported metrics, can be shown by enabling ` --remoteRead.showURL`;