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 <roman@victoriametrics.com>
This commit is contained in:
Roman Khavronenko 2022-05-30 11:16:24 +02:00 committed by GitHub
parent 3299865620
commit 46c06334ee
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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,