From 46c06334eef7bcf1e903dad0c9b45a19e6e0922c Mon Sep 17 00:00:00 2001 From: Roman Khavronenko Date: Mon, 30 May 2022 11:16:24 +0200 Subject: [PATCH] dashboards: use `vm_concurrent_select_current` instead of `vm_concurrent_queries` (#2655) Using metric `vm_concurrent_queries` in relation to `vm_concurrent_select_capacity` is incorrect. Switching to `vm_concurrent_select_current` in `Concurrent selects` panel. Signed-off-by: hagen1778 --- dashboards/victoriametrics.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dashboards/victoriametrics.json b/dashboards/victoriametrics.json index bced613e88..0d1de94e46 100644 --- a/dashboards/victoriametrics.json +++ b/dashboards/victoriametrics.json @@ -5630,7 +5630,7 @@ "steppedLine": false, "targets": [ { - "expr": "sum(max_over_time(vm_concurrent_queries{job=~\"$job_select\", instance=~\"$instance\"}[1m]))", + "expr": "sum(max_over_time(vm_concurrent_select_current{job=~\"$job_select\", instance=~\"$instance\"}[1m]))", "format": "time_series", "interval": "", "intervalFactor": 1,