mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2026-06-25 11:38:49 +03:00
f99e49c15d
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>
VictoriaMetrics dashboards
The directory contains the official list of Grafana dashboards for VictoriaMetrics components.
The vm folder contains copies of the listed dashboards but alternated to use
VictoriaMetrics datasource.
The listed dashboards can be found on Grafana website.
When making changes to the dashboards in dashboards folder, don't forget to call make dashboards-sync
and sync changes to Grafana website.