clarify cluster multitenacy in vmanomaly docs (#5619)

Signed-off-by: Artem Navoiev <tenmozes@gmail.com>
This commit is contained in:
Artem Navoiev 2024-01-15 12:36:28 -08:00 committed by GitHub
parent f51b7fda8e
commit 0c78b891b0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View file

@ -53,7 +53,7 @@ Future updates will introduce additional readers, expanding the range of data so
<tr>
<td><code>tenant_id</code></td>
<td><code>"0:0"</code></td>
<td>For cluster version only, tenants are identified by accountID or accountID:projectID</td>
<td>For VictoriaMetrics Cluster version only, tenants are identified by accountID or accountID:projectID. See VictoriaMetrics Cluster [multitenancy docs](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#multitenancy)</td>
</tr>
<tr>
<td><code>sampling_period</code></td>

View file

@ -46,7 +46,7 @@ Future updates will introduce additional export methods, offering users more fle
<tr>
<td><code>tenant_id</code></td>
<td><code>"0:0"</code></td>
<td>For cluster version only, tenants are identified by accountID or accountID:projectID</td>
<td>For VictoriaMetrics Cluster version only, tenants are identified by accountID or accountID:projectID. See VictoriaMetrics Cluster [multitenancy docs](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#multitenancy)</td>
</tr>
<!-- Additional rows for metric_format -->
<tr>