hagen1778 d4b56d467f dashboards: show max number of active merges instead of cumulative ... The cumulative number of active merges could be red herring as it its value depends on the number of vmstorages. For example, vmstorage could be added or removed and this will affect the panel. Or, each vmstorage could start a merging process (i.e. for downsampling) and visiually it could look like a massive change. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 035de57e5e)		2024-04-24 17:08:15 +02:00
..
victoriametrics-cluster.json	dashboards: show max number of active merges instead of cumulative	2024-04-24 17:08:15 +02:00
victoriametrics.json	all: replace old https://docs.victoriametrics.com/MetricsQL.html url with the new one - https://docs.victoriametrics.com/metricsql/	2024-04-18 02:15:33 +02:00
vmagent.json	all: replace remaining https://docs.victoriametrics.com/vmagent.html urls with the new one - https://docs.victoriametrics.com/vmagent/	2024-04-18 01:36:20 +02:00
vmalert.json	all: replace old https://docs.victoriametrics.com/Troubleshooting.html url with the new one - https://docs.victoriametrics.com/troubleshooting/	2024-04-18 03:27:18 +02:00