VictoriaMetrics

mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2026-06-27 20:47:28 +03:00

Files

Roman Khavronenko f99e49c15d dashboards/victoriametrics-cluster: show max 99th percentile on vmselect panels (#9555 )

Before, we showed summarized 99th percentile for query complexity across
all available instance. This doesn't make much sense, as it doesn't
answer on the following questions:
1. What complexity limits to set per vmselect
2. What are the most expensive queries

The change is to use `max` instead of `sum`, to show only outliers, the
heaviest served queries. The update should help answering on questions
above.

### Describe Your Changes

Please provide a brief description of the changes you made. Be as
specific as possible to help others understand the purpose and impact of
your modifications.

### Checklist

The following checks are **mandatory**:

- [ ] My change adheres to [VictoriaMetrics contributing
guidelines](https://docs.victoriametrics.com/victoriametrics/contributing/#pull-request-checklist).
- [ ] My change adheres to [VictoriaMetrics development
goals](https://docs.victoriametrics.com/victoriametrics/goals/).

Signed-off-by: hagen1778 <roman@victoriametrics.com>

2025-08-12 16:43:07 +02:00

backupmanager.json

dashboards: drop all dashboards tags except victoriametrics or victorialogs tags for consistency (#8620 )

2025-03-31 14:27:05 +02:00

clusterbytenant.json

use new canonical urls to cluster-victoriametrics docs: https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/

2025-04-30 18:52:12 +02:00

operator.json

dashboards: drop all dashboards tags except victoriametrics or victorialogs tags for consistency (#8620 )

2025-03-31 14:27:05 +02:00

victoriametrics-cluster.json

dashboards/victoriametrics-cluster: show max 99th percentile on vmselect panels (#9555 )