github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2025-03-21 15:45:01 +00:00
Code Issues Projects Releases Packages Wiki Activity
VictoriaMetrics/dashboards/victoriametrics.json

6402 lines
187 KiB
JSON
Raw Permalink Normal View History

Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
"annotations": {
"list": [
{
"builtIn": 1,
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"datasource": {
"type": "datasource",
"uid": "grafana"
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"enable": true,
"hide": true,
"iconColor": "rgba(0, 211, 255, 1)",
"name": "Annotations & Alerts",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"target": {
"limit": 100,
"matchAny": false,
"tags": [],
"type": "dashboard"
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"type": "dashboard"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"enable": true,
deployment/dashboards: respect `job` and `instance` filters for `alerts` annotation in cluster and single-node dashboards Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit d6ae08259856f36022d72f157a1b585f1375b825)
2023-11-14 08:38:15 +00:00
"expr": "sum(ALERTS{job=~\"$job\", instance=~\"$instance\", alertgroup=\"vmsingle\",alertstate=\"firing\",show_at=\"dashboard\"}) by(alertname)",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hide": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"iconColor": "red",
"name": "alerts",
"titleFormat": "{{alertname}}"
dashboards: add VersionChange annotation (#3473) The new annotation is hidden by default and suppose to show component `short_version` label change on the panels. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-12-12 15:32:26 +00:00
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"enable": true,
dashboards: use `$__interval` variable for offsets and look-behind windows in annotations This should improve precision of `restarts` and `version change` annotations when zooming-in/zooming-out on the dashboards. The change also makes `restarts` dashboard visible on the panels, so user can disable it from displaying if needed. This could be useful when restarts overlap with version change events. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9dd9b4442f7a64b9d0f662a8354a1b6cd5d08a63)
2024-05-22 14:32:51 +00:00
"expr": "sum(vm_app_version{job=~\"$job\", instance=~\"$instance\"}) by(version) unless (sum(vm_app_version{job=~\"$job\", instance=~\"$instance\"} offset $__interval) by(version))",
dashboards: add VersionChange annotation (#3473) The new annotation is hidden by default and suppose to show component `short_version` label change on the panels. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-12-12 15:32:26 +00:00
"hide": true,
"iconColor": "dark-blue",
"name": "version",
dashboards: use `version` instead of `short_version` in annotations `version` label won't show the difference if various flavors of the same version were deployed. But `short_version` will. For example, on the sandbox env we test VM builds before new version release. Without this change, the version update won't be visible on dashboard. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit d389a4fcf34528bb8ff9086813f20667de1742d8)
2023-11-16 08:26:47 +00:00
"textFormat": "{{version}}",
dashboards: add VersionChange annotation (#3473) The new annotation is hidden by default and suppose to show component `short_version` label change on the panels. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-12-12 15:32:26 +00:00
"titleFormat": "Version change"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"description": "Overview for single-node VictoriaMetrics v1.102.0 or higher",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"editable": true,
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"fiscalYearStartMonth": 0,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"graphTooltip": 1,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"id": 1,
add links and fix cache metric name (#233)
2019-11-12 13:06:56 +00:00
"links": [
{
"icon": "doc",
"tags": [],
"targetBlank": true,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"title": "Single server Wiki",
add links and fix cache metric name (#233)
2019-11-12 13:06:56 +00:00
"type": "link",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"url": "https://docs.victoriametrics.com/"
add links and fix cache metric name (#233)
2019-11-12 13:06:56 +00:00
},
{
"icon": "external link",
"tags": [],
"targetBlank": true,
"title": "Found a bug?",
"type": "link",
"url": "https://github.com/VictoriaMetrics/VictoriaMetrics/issues"
},
{
"icon": "external link",
"tags": [],
"targetBlank": true,
"title": "New releases",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"tooltip": "",
add links and fix cache metric name (#233)
2019-11-12 13:06:56 +00:00
"type": "link",
"url": "https://github.com/VictoriaMetrics/VictoriaMetrics/releases"
}
],
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"panels": [
{
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"collapsed": false,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 1,
"w": 24,
"x": 0,
"y": 0
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"id": 6,
"panels": [],
"title": "Stats",
"type": "row"
},
{
"description": "",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"fieldConfig": {
"defaults": {},
"overrides": []
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"gridPos": {
"h": 2,
"w": 4,
"x": 0,
"y": 1
},
"id": 85,
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"code": {
"language": "plaintext",
"showLineNumbers": false,
"showMiniMap": false
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"content": "<div style=\"text-align: center;\">$version</div>",
"mode": "markdown"
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"title": "Version",
"type": "text"
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
"description": "How many datapoints are in storage",
"fieldConfig": {
"defaults": {
"color": {
"mode": "thresholds"
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
}
]
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "short"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
"gridPos": {
"h": 2,
"w": 5,
"x": 4,
"y": 1
},
"id": 26,
"maxDataPoints": 100,
"options": {
"colorMode": "value",
"graphMode": "area",
"justifyMode": "auto",
"orientation": "horizontal",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"percentChangeColorMode": "standard",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"reduceOptions": {
"calcs": [
"lastNotNull"
],
"fields": "",
"values": false
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"showPercentChange": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"text": {},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"textMode": "auto",
"wideLayout": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"targets": [
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"exemplar": false,
{dashboards,alerts}: subtitute `{type="indexdb"}` with `{type=~"indexdb.*"}` inside queries after 8189770c50165b62867327ad388f2c2ef237ab6f Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3337
2022-12-05 23:59:52 +00:00
"expr": "sum(vm_rows{job=~\"$job\", instance=~\"$instance\", type!~\"indexdb.*\"})",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"instant": true,
"interval": "",
"intervalFactor": 1,
"legendFormat": "",
"refId": "A"
}
],
"title": "Total datapoints",
"type": "stat"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "Shows the datapoints ingestion rate.",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "thresholds"
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
}
]
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "short"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
"gridPos": {
"h": 2,
"w": 5,
"x": 9,
"y": 1
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 107,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"maxDataPoints": 100,
"options": {
"colorMode": "value",
"graphMode": "area",
"justifyMode": "auto",
"orientation": "horizontal",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"percentChangeColorMode": "standard",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"reduceOptions": {
"calcs": [
"lastNotNull"
],
"fields": "",
"values": false
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"showPercentChange": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"text": {},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"textMode": "auto",
"wideLayout": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"targets": [
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"exemplar": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"expr": "sum(rate(vm_rows_inserted_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval]))",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"instant": true,
"interval": "",
"intervalFactor": 1,
"legendFormat": "",
"refId": "A"
}
],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"title": "Ingestion rate",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"type": "stat"
},
{
"datasource": {
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "Shows the rate of HTTP read requests.",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "thresholds"
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
}
]
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "short"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
"gridPos": {
"h": 2,
"w": 5,
"x": 14,
"y": 1
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 108,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"maxDataPoints": 100,
"options": {
"colorMode": "value",
"graphMode": "area",
"justifyMode": "auto",
"orientation": "horizontal",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"percentChangeColorMode": "standard",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"reduceOptions": {
"calcs": [
"lastNotNull"
],
"fields": "",
"values": false
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"showPercentChange": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"text": {},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"textMode": "auto",
"wideLayout": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"targets": [
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
"exemplar": false,
"expr": "sum(rate(vm_http_requests_total{job=~\"$job\", instance=~\"$instance\", path!~\".*(/write|/metrics)\"}[$__rate_interval]))",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"instant": true,
"interval": "",
"intervalFactor": 1,
"legendFormat": "",
"refId": "A"
}
],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"title": "Read requests",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"type": "stat"
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "Total number of available CPUs for VM process",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "thresholds"
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
}
]
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "short"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
"gridPos": {
"h": 2,
"w": 5,
"x": 19,
"y": 1
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 77,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"maxDataPoints": 100,
"options": {
"colorMode": "value",
"graphMode": "area",
"justifyMode": "auto",
"orientation": "horizontal",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"percentChangeColorMode": "standard",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"reduceOptions": {
"calcs": [
"lastNotNull"
],
"fields": "",
"values": false
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"showPercentChange": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"text": {},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"textMode": "auto",
"wideLayout": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"targets": [
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"exemplar": false,
"expr": "sum(vm_available_cpu_cores{job=~\"$job\", instance=~\"$instance\"})",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"instant": true,
"interval": "",
"intervalFactor": 1,
"legendFormat": "",
"refId": "A"
}
],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"title": "Available CPU",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"type": "stat"
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
"fieldConfig": {
"defaults": {
"color": {
"mode": "thresholds"
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "red",
"value": null
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
{
"color": "green",
"value": 1800
}
]
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "s"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
"gridPos": {
"h": 2,
"w": 4,
"x": 0,
"y": 3
},
"id": 87,
"options": {
"colorMode": "value",
"graphMode": "area",
"justifyMode": "auto",
"orientation": "auto",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"percentChangeColorMode": "standard",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"reduceOptions": {
"calcs": [
"lastNotNull"
],
"fields": "",
"values": false
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"showPercentChange": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"text": {},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"textMode": "auto",
"wideLayout": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"targets": [
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
"exemplar": false,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "min(vm_app_uptime_seconds{job=~\"$job\", instance=~\"$instance\"})",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"instant": true,
"interval": "",
"legendFormat": "",
"refId": "A"
}
],
"title": "Uptime",
"type": "stat"
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards: update links in various panels * use docs.victoriametrics.com instead of github docs * add links to common terms used in VictoriaMetrics Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-03-04 14:43:31 +00:00
"description": "Shows the number of [active time series](https://docs.victoriametrics.com/faq/#what-is-an-active-time-series) with new data points inserted during the last hour. High value may result in ingestion slowdown.",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "thresholds"
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
}
]
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "short"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
"gridPos": {
"h": 2,
"w": 5,
"x": 4,
"y": 3
},
"id": 38,
"maxDataPoints": 100,
"options": {
"colorMode": "value",
"graphMode": "area",
"justifyMode": "auto",
"orientation": "horizontal",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"percentChangeColorMode": "standard",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"reduceOptions": {
"calcs": [
"lastNotNull"
],
"fields": "",
"values": false
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"showPercentChange": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"text": {},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"textMode": "auto",
"wideLayout": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"targets": [
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"exemplar": false,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(vm_cache_entries{job=~\"$job\", instance=~\"$instance\", type=\"storage/hour_metric_ids\"})",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"instant": true,
"interval": "",
"intervalFactor": 1,
"legendFormat": "",
"refId": "A"
}
],
dashboards: replace `Index size` panel with `Active series` (#3157) Panel `Index size` showed itself impractical for users. So replacing it with `Active series` panel. https://github.com/VictoriaMetrics/VictoriaMetrics/issues/776#issuecomment-1255823734 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-25 19:49:18 +00:00
"title": "Active series",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"type": "stat"
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "Total amount of used disk space",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "thresholds"
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"mappings": [],
"thresholds": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "absolute",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"steps": [
{
"color": "green",
"value": null
}
]
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "bytes"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
"gridPos": {
"h": 2,
"w": 5,
"x": 9,
"y": 3
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 81,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"maxDataPoints": 100,
"options": {
"colorMode": "value",
"graphMode": "area",
"justifyMode": "auto",
"orientation": "horizontal",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"percentChangeColorMode": "standard",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"reduceOptions": {
"calcs": [
"lastNotNull"
],
"fields": "",
"values": false
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"showPercentChange": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"text": {},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"textMode": "auto",
"wideLayout": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"targets": [
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"uid": "$ds"
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
"exemplar": false,
"expr": "sum(vm_data_size_bytes{job=~\"$job\", instance=~\"$instance\"})",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"instant": true,
"interval": "",
"intervalFactor": 1,
"legendFormat": "",
"refId": "A"
}
],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"title": "Disk space usage",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"type": "stat"
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "Average disk usage per datapoint.",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "thresholds"
},
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
dashboards: migrate from old table panel in cluster dashboard (#1993) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-22 09:21:06 +00:00
{
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"color": "green",
"value": null
dashboards: migrate from old table panel in cluster dashboard (#1993) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-22 09:21:06 +00:00
}
Dashboar cluster update (#2674) * dashboard: fix query for `CPU percentage` panel Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboard: replace Uptime panel with Version panel Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-02 14:03:48 +00:00
]
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "bytes"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
"gridPos": {
"h": 2,
"w": 5,
"x": 14,
"y": 3
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 82,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"maxDataPoints": 100,
"options": {
"colorMode": "value",
"graphMode": "area",
"justifyMode": "auto",
"orientation": "horizontal",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"percentChangeColorMode": "standard",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"reduceOptions": {
"calcs": [
"lastNotNull"
],
"fields": "",
"values": false
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"showPercentChange": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"text": {},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"textMode": "auto",
"wideLayout": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"targets": [
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
"exemplar": false,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "max(sum(vm_data_size_bytes{job=~\"$job\", instance=~\"$instance\"}) / sum(vm_rows{job=~\"$job\", instance=~\"$instance\"}))",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"instant": true,
"interval": "",
"intervalFactor": 1,
"legendFormat": "",
"refId": "A"
}
],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"title": "Bytes per point",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"type": "stat"
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
"description": "Total size of available memory for VM process",
"fieldConfig": {
"defaults": {
"color": {
"mode": "thresholds"
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
}
]
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "bytes"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
"gridPos": {
"h": 2,
"w": 5,
"x": 19,
"y": 3
},
"id": 78,
"maxDataPoints": 100,
"options": {
"colorMode": "value",
"graphMode": "area",
"justifyMode": "auto",
"orientation": "horizontal",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"percentChangeColorMode": "standard",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"reduceOptions": {
"calcs": [
"lastNotNull"
],
"fields": "",
"values": false
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"showPercentChange": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"text": {},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"textMode": "auto",
"wideLayout": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"targets": [
{
"datasource": {
"uid": "$ds"
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"exemplar": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"expr": "sum(vm_available_memory_bytes{job=~\"$job\", instance=~\"$instance\"})",
"format": "time_series",
"instant": true,
"interval": "",
"intervalFactor": 1,
"legendFormat": "",
"refId": "A"
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
}
],
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"title": "Available memory",
"type": "stat"
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
},
{
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
"collapsed": false,
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
"gridPos": {
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
"h": 1,
"w": 24,
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
"x": 0,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"y": 5
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"id": 24,
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
"panels": [],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"title": "Overview",
Dashboard cluster (#1375) * dashboard: update vmagent dash The update contains the following changes: * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0 * dashboard: update cluster dash The update contains the following changes: * move stats panels to Configuration row, so it can be collapsed; * display anonymous memory usage metric. This metric suppose to reflect memory usage of the process which can't be freed by OS; * add legends to all panels. This is important for cases when users share the screenshots; * modify panels for Grafana v8.0.0
2021-06-14 10:03:54 +00:00
"type": "row"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "How many datapoints are inserted into storage per second",
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
},
{
"color": "red",
"value": 80
}
]
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "short"
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"y": 6
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 106,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(rate(vm_rows_inserted_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (type, instance) > 0",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"hide": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{type}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Datapoints ingestion rate",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "* `*` - unsupported query path\n* `/write` - insert into VM\n* `/metrics` - query VM system metrics\n* `/query` - query instant values\n* `/query_range` - query over a range of time\n* `/series` - match a certain label set\n* `/label/{}/values` - query a list of label values (variables mostly)",
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
},
{
"color": "red",
"value": 80
}
]
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "short"
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"y": 6
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 12,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(rate(vm_http_requests_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (path, instance) > 0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"format": "time_series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{path}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Requests rate",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update links in various panels * use docs.victoriametrics.com instead of github docs * add links to common terms used in VictoriaMetrics Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-03-04 14:43:31 +00:00
"description": "Shows the number of [active time series](https://docs.victoriametrics.com/faq/#what-is-an-active-time-series) with new data points inserted during the last hour. High value may result in ingestion slowdown. \n\nSee following link for details:",
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
},
{
"color": "red",
"value": 80
}
]
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "short"
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"y": 14
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"id": 51,
"links": [
{
"targetBlank": true,
"title": "troubleshooting",
dashboards: update links in various panels * use docs.victoriametrics.com instead of github docs * add links to common terms used in VictoriaMetrics Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-03-04 14:43:31 +00:00
"url": "https://docs.victoriametrics.com/troubleshooting"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
}
],
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"expr": "vm_cache_entries{job=~\"$job\", instance=~\"$instance\", type=\"storage/hour_metric_ids\"}",
dashboards: updates and fixes for cluster version (#500) * The new update introduces new row "Troubleshooting" that contains panels for churn rate and slow-queries/inserts/loads metrics. This row supposed to be reveal the cause of low performance or other issues; * CPU panel got `short` units instead of `seconds`; * Overview row was updated with panel showing bytes-per-datapoint stat; * Overview row was updated with panel showing free disk space.
2020-05-19 08:57:20 +00:00
"format": "time_series",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}}",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Active time series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "The less time it takes is better.\n* `*` - unsupported query path\n* `/write` - insert into VM\n* `/metrics` - query VM system metrics\n* `/query` - query instant values\n* `/query_range` - query over a range of time\n* `/series` - match a certain label set\n* `/label/{}/values` - query a list of label values (variables mostly)",
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
},
{
"color": "red",
"value": 80
}
]
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "s"
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"y": 14
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 22,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "max(vm_request_duration_seconds{job=~\"$job\", instance=~\"$instance\", quantile=\"0.99\"}) by (instance, path) > 0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"format": "time_series",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{path}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Query duration 0.99 quantile",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "* `*` - unsupported query path\n* `/write` - insert into VM\n* `/metrics` - query VM system metrics\n* `/query` - query instant values\n* `/query_range` - query over a range of time\n* `/series` - match a certain label set\n* `/label/{}/values` - query a list of label values (variables mostly)",
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
},
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
"unit": "short"
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 0,
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
"y": 22
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 35,
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
"exemplar": false,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(rate(vm_http_request_errors_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance, path) > 0",
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
"format": "time_series",
"interval": "",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{path}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Requests error rate",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "Shows the rate of logging the messages by their level. Unexpected spike in rate is a good reason to check logs.",
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "bars",
"fillOpacity": 100,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "auto",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
deployment: bump Grafana version to 10.4.2 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9256df17fa808529930ca38eb3e423276ffbefda)
2024-04-29 10:10:24 +00:00
}
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"y": 22
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 110,
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"lastNotNull",
"mean",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "single",
"sort": "none"
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(rate(vm_log_messages_total{job=~\"$job\", instance=~\"$instance\", level!=\"info\"}[$__rate_interval])) by (instance, level, location) > 0",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "5m",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{level}}: {{location}}",
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
"range": true,
"refId": "A"
}
],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"title": "Logging rate",
"type": "timeseries"
Dashboards (#3120) * dashboards/cluster: few updates * apply consistent formatting across panels; * make resource usage panels per component more detailed; * add extra panels to vmselect for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/single: few updates * apply consistent formatting across panels; * add extra panels to Performance for displaying `vm_rows_read_per_query`, `vm_rows_scanned_per_query`, `vm_rows_read_per_series` and `vm_series_read_per_query` metrics. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: few updates * apply consistent formatting across panels; * add panels for showing number of samples ingested or scraped; * adapt resource usage panels for multiple selected jobs/instances; * add adhoc variable; * display vmagent's version in Stats. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmalert: few updates * apply consistent formatting across panels; * adapt resource usage panels for multiple selected jobs/instances; * show vmalert version in Stats section. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-09-16 19:24:32 +00:00
},
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
{
"collapsed": true,
"gridPos": {
"h": 1,
"w": 24,
"x": 0,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"y": 30
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 46,
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
"panels": [
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update description for RSS and anonymous memory panels to be consistent for single-node, cluster and vmagent dashboards. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit d3ae2b2f62ddb631bb7d9afc5ad380785bada187)
2023-11-14 08:50:06 +00:00
"description": "Percentage of used RSS memory (resident).\nThe RSS memory shows the amount of memory recently accessed by the application. It includes anonymous memory and data from recently accessed files (aka page cache).\nThe application's performance will significantly degrade when memory usage is close to 100%.\n\nClick on the line and choose Drilldown to show memory usage per instance",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
},
dashboards: remove DataLinks from single version (#3456) Those data links were copy&paste artifact from cluster version and aren't needed on the dash. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-12-07 13:35:52 +00:00
"links": [],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"unit": "percentunit"
dashboard: set Y-min to zero for most of panels in cluster dashboard (#737) Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-09-02 12:15:13 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 31
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 112,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
"exemplar": false,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"expr": "max(\n max_over_time(process_resident_memory_bytes{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])\n /\n vm_available_memory_bytes{job=~\"$job\", instance=~\"$instance\"}\n) by(instance)",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "",
"legendFormat": "__auto",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "RSS memory % usage",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"description": "",
dashboard: set Y-min to zero for most of panels in cluster dashboard (#737) Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-09-02 12:15:13 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
dashboards: remove DataLinks from single version (#3456) Those data links were copy&paste artifact from cluster version and aren't needed on the dash. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-12-07 13:35:52 +00:00
"links": [],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"unit": "bytes"
dashboard: set Y-min to zero for most of panels in cluster dashboard (#737) Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-09-02 12:15:13 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 31
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"id": 44,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"sort": "desc"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(go_memstats_sys_bytes{job=~\"$job\", instance=~\"$instance\"}) by (instance) + sum(vm_cache_size_bytes{job=~\"$job\", instance=~\"$instance\"}) by (instance)",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"format": "time_series",
"hide": false,
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - requested from system",
"range": true,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"refId": "A"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(go_memstats_heap_inuse_bytes{job=~\"$job\", instance=~\"$instance\"}) by (instance) + sum(vm_cache_size_bytes{job=~\"$job\", instance=~\"$instance\"}) by (instance)",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"format": "time_series",
"hide": false,
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - heap inuse",
"range": true,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"refId": "B"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(go_memstats_stack_inuse_bytes{job=~\"$job\", instance=~\"$instance\"}) by (instance)",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"format": "time_series",
"hide": false,
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - stack inuse",
"range": true,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"refId": "C"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(process_resident_memory_bytes{job=~\"$job\", instance=~\"$instance\"}) by (instance)",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"format": "time_series",
"hide": false,
"interval": "",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - resident",
"range": true,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"refId": "D"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"exemplar": false,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(process_resident_memory_anon_bytes{job=~\"$job\", instance=~\"$instance\"}) by (instance)",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"format": "time_series",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"hide": false,
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
"interval": "",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - resident anonymous",
"range": true,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"refId": "E"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Memory usage",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update description for RSS and anonymous memory panels to be consistent for single-node, cluster and vmagent dashboards. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit d3ae2b2f62ddb631bb7d9afc5ad380785bada187)
2023-11-14 08:50:06 +00:00
"description": "Share for memory allocated by the process itself. When memory usage reaches 100% it will be likely OOM-killed.\nSafe memory usage % considered to be below 80%\n\nClick on the line and choose Drilldown to show memory usage per instance",
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"unit": "percentunit"
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 39
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"id": 123,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
}
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"editorMode": "code",
"exemplar": false,
"expr": "max(\n max_over_time(process_resident_memory_anon_bytes{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])\n /\n vm_available_memory_bytes{job=~\"$job\", instance=~\"$instance\"}\n) by(instance)",
"interval": "",
"legendFormat": "__auto",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "RSS anonymous memory % usage",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"type": "timeseries"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"unit": "percentunit"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 39
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
},
"id": 114,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"targets": [
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"editorMode": "code",
"exemplar": false,
dashboards: consistently use `process_cpu_cores_available` for CPU usage Related issue: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7988 --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 5a1a28ba873029f2a1373ea68e236ee48a5138da)
2025-01-28 12:58:06 +00:00
"expr": "max(\n rate(process_cpu_seconds_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])\n /\n process_cpu_cores_available{job=~\"$job\", instance=~\"$instance\"}\n) by(instance)",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"intervalFactor": 1,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"legendFormat": "__auto",
"range": true,
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "CPU % usage",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"type": "timeseries"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "Shows the percentage of open file descriptors compared to the limit set in the OS.\nReaching the limit of open files can cause various issues and must be prevented.\n\nSee how to change limits here https://medium.com/@muhammadtriwibowo/set-permanently-ulimit-n-open-files-in-ubuntu-4d61064429a",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 2,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
},
{
"color": "red",
"value": 80
}
]
},
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"unit": "percentunit"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"overrides": [
{
"matcher": {
"id": "byName",
"options": "max"
},
"properties": [
{
"id": "color",
"value": {
"fixedColor": "#C4162A",
"mode": "fixed"
}
}
]
}
]
},
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 47
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
},
"id": 75,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"targets": [
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"editorMode": "code",
"expr": "max_over_time(process_open_fds{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])\n/\nprocess_max_fds{job=~\"$job\", instance=~\"$instance\"}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"format": "time_series",
"hide": false,
"interval": "",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"intervalFactor": 2,
"legendFormat": "{{instance}}",
"range": true,
"refId": "A"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Open FDs",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"description": "CPU cores used by instance",
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"unit": "short"
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"overrides": [
{
"matcher": {
"id": "byName",
"options": "Limit"
},
"properties": [
{
"id": "color",
"value": {
"fixedColor": "#F2495C",
"mode": "fixed"
}
}
]
}
]
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 47
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 57,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"expr": "rate(process_cpu_seconds_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"format": "time_series",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"interval": "",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}}",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"exemplar": false,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "min(process_cpu_cores_available{job=~\"$job\", instance=~\"$instance\"})",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"hide": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"interval": "",
"intervalFactor": 1,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legendFormat": "Limit",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"range": true,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"refId": "B"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "CPU",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"fillOpacity": 10,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"decimals": 0,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"unit": "short"
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"overrides": []
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 55
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"id": 47,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"expr": "sum(go_goroutines{job=~\"$job\", instance=~\"$instance\"}) by(instance)",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"intervalFactor": 2,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"legendFormat": "{{instance}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
"refId": "A"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Goroutines",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "Shows the number of bytes read/write from the storage layer.",
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"unit": "bytes"
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"overrides": [
{
"matcher": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"id": "byRegexp",
"options": "/.*read/"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"properties": [
{
"id": "custom.transform",
"value": "negative-Y"
}
]
}
]
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 55
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"id": 76,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(rate(process_io_storage_read_bytes_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance)",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"hide": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"interval": "",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - read",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
},
{
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(rate(process_io_storage_written_bytes_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance)",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"format": "time_series",
"hide": false,
"interval": "",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - write",
"range": true,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"refId": "B"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Disk writes/reads",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 0,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"unit": "short"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 63
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"id": 48,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"editorMode": "code",
"expr": "sum(process_num_threads{job=~\"$job\", instance=~\"$instance\"}) by(instance)",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"format": "time_series",
"intervalFactor": 2,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"legendFormat": "{{instance}}",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Threads",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
add description, churn rate panel, storage.ingestion rate panel (#228)
2019-11-10 18:32:10 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"description": "Shows the number of read/write syscalls such as read, pread, write, pwrite.",
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"unit": "short"
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"overrides": [
{
"matcher": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"id": "byRegexp",
"options": "/.*read.*/"
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
},
"properties": [
{
"id": "custom.transform",
"value": "negative-Y"
}
]
}
]
dashboard: update cluster-version dashboard. (#558) Fix "Bytes per point" panel query #551.
2020-06-12 19:07:28 +00:00
},
add description, churn rate panel, storage.ingestion rate panel (#228)
2019-11-10 18:32:10 +00:00
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 63
add description, churn rate panel, storage.ingestion rate panel (#228)
2019-11-10 18:32:10 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"id": 124,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
add description, churn rate panel, storage.ingestion rate panel (#228)
2019-11-10 18:32:10 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(rate(process_io_read_syscalls_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance)",
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
"format": "time_series",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"hide": false,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"interval": "",
dashboard: update cluster node dashboard (#1136) * add panel `Open FDs` for file descriptors metrics; * add panel `Disk writes/reads` to show the real read/write load on storage layer; * add stats panel to show available CPUs, memory and disk space.
2021-03-18 10:04:12 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - read calls",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"range": true,
add description, churn rate panel, storage.ingestion rate panel (#228)
2019-11-10 18:32:10 +00:00
"refId": "A"
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(rate(process_io_write_syscalls_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance)",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"format": "time_series",
"hide": false,
"interval": "",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - write calls",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"range": true,
"refId": "B"
add description, churn rate panel, storage.ingestion rate panel (#228)
2019-11-10 18:32:10 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Disk write/read calls",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"description": "",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"unit": "short"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 71
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"id": 49,
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"targets": [
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"editorMode": "code",
"expr": "sum(rate(vm_tcplistener_accepts_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by(instance)",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"format": "time_series",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"hide": false,
"intervalFactor": 1,
"legendFormat": "{{instance}}",
"range": true,
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "TCP connections rate",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"unit": "short"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"overrides": []
},
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 71
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"id": 37,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"targets": [
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"expr": "sum(vm_tcplistener_conns{job=~\"$job\", instance=~\"$instance\"}) by(instance)",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"hide": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"intervalFactor": 1,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"legendFormat": "{{instance}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"refId": "A"
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "TCP connections",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
},
dashboards: add `Network Usage` panel to `Resource Usage` row https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4478 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 8606b48ce5df3f4e1a2edef1acae8e98d0189d00)
2024-04-29 09:54:17 +00:00
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "Shows network usage by VM:\n* Writes show traffic sent to clients\n* Reads show traffic received from clients",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
"axisBorderShow": false,
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards: add `Network Usage` panel to `Resource Usage` row https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4478 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 8606b48ce5df3f4e1a2edef1acae8e98d0189d00)
2024-04-29 09:54:17 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
"insertNulls": false,
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards: add `Network Usage` panel to `Resource Usage` row https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4478 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 8606b48ce5df3f4e1a2edef1acae8e98d0189d00)
2024-04-29 09:54:17 +00:00
},
{
"color": "red",
"value": 80
}
]
},
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"unit": "decbits"
dashboards: add `Network Usage` panel to `Resource Usage` row https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4478 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 8606b48ce5df3f4e1a2edef1acae8e98d0189d00)
2024-04-29 09:54:17 +00:00
},
"overrides": [
{
"matcher": {
"id": "byRegexp",
"options": "/read.*/"
},
"properties": [
{
"id": "custom.transform",
"value": "negative-Y"
}
]
}
]
},
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 79
dashboards: add `Network Usage` panel to `Resource Usage` row https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4478 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 8606b48ce5df3f4e1a2edef1acae8e98d0189d00)
2024-04-29 09:54:17 +00:00
},
"id": 127,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards: add `Network Usage` panel to `Resource Usage` row https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4478 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 8606b48ce5df3f4e1a2edef1acae8e98d0189d00)
2024-04-29 09:54:17 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
dashboards: add `Network Usage` panel to `Resource Usage` row https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4478 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 8606b48ce5df3f4e1a2edef1acae8e98d0189d00)
2024-04-29 09:54:17 +00:00
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"expr": "sum(rate(vm_tcplistener_read_bytes_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by(name) * 8 > 0",
"format": "time_series",
"hide": false,
"intervalFactor": 1,
"legendFormat": "read via {{name}}",
"range": true,
"refId": "A"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"expr": "sum(rate(vm_tcplistener_written_bytes_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by(name) * 8 > 0",
"format": "time_series",
"hide": false,
"intervalFactor": 1,
"legendFormat": "write via {{name}}",
"range": true,
"refId": "B"
}
],
"title": "Network usage",
"type": "timeseries"
},
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "Shows the percent of CPU spent on garbage collection.\n\nIf % is high, then CPU usage can be decreased by changing GOGC to higher values. Increasing GOGC value will increase memory usage, and decrease CPU usage.\n\nTry searching for keyword `GOGC` at https://docs.victoriametrics.com/troubleshooting/ ",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
"axisBorderShow": false,
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
"insertNulls": false,
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 0,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
},
{
"color": "red",
"value": 80
}
]
},
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"unit": "percentunit"
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
dashboards: add `Network Usage` panel to `Resource Usage` row https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4478 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 8606b48ce5df3f4e1a2edef1acae8e98d0189d00)
2024-04-29 09:54:17 +00:00
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 79
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
},
"id": 125,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"expr": "max(\n rate(go_gc_cpu_seconds_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval]) \n / rate(process_cpu_seconds_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])\n ) by(instance)",
"format": "time_series",
"interval": "",
"intervalFactor": 2,
"legendFormat": "__auto",
"range": true,
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "CPU spent on GC",
dashboards/all: add new panel `CPU spent on GC` It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 15:21:21 +00:00
"type": "timeseries"
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "Shows the time goroutines have spent in runnable state before actually running. The lower is better.\n\nHigh values or values exceeding the threshold is usually a sign of insufficient CPU resources or CPU throttling. \n\nVerify that service has enough CPU resources. Otherwise, the service could work unreliably with delays in processing.",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
"axisBorderShow": false,
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"barWidthFactor": 0.6,
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
"insertNulls": false,
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "line"
}
},
"decimals": 0,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green",
"value": null
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
},
{
"color": "red",
"value": 0.1
}
]
},
"unit": "s"
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 87
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
},
"id": 128,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true
},
"tooltip": {
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"hideZeros": false,
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"pluginVersion": "11.5.0",
deployment: add panel and alerts for displying go scheduler latency (#7078) The panel and alerting rule should help to understand whether VM component doesn't have enough CPU resources or gets throttled. The alert is applicable for all VM components. The panel was added to vmalert, vmagent, vmsingle, vm clusert and victorialogs dashes. ------------------- This alerting rule should have help us identify resource shortage for sandbox vmagent - see [this link](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/prometheus/graph/#/?g0.range_input=23d13h25m25s424ms&g0.end_input=2024-09-23T14%3A11%3A00&g0.relative_time=none&g0.tab=0&g0.expr=histogram_quantile%280.99%2C+sum%28rate%28go_sched_latencies_seconds_bucket%7Bjob%3D%22vmagent-monitoring-vmagent%22%7D%5B5m%5D%29%29+by+%28le%2C+job%2C+instance%29%29+%3E+0.1) for example. We weren't aware of resource shortage, because VM metrics assumed this vmagent had 1vCPU while in fact its limit was 0.2vCPU. Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 4d0b41e63b96fcf338026c8cac12322f37588565)
2024-09-23 14:54:42 +00:00
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"expr": "histogram_quantile(0.99, sum(rate(go_sched_latencies_seconds_bucket{job=~\"$job\"}[$__rate_interval])) by (job, instance, le))",
"format": "time_series",
"interval": "",
"intervalFactor": 2,
"legendFormat": "__auto",
"range": true,
"refId": "A"
}
],
"title": "Go scheduling latency",
"type": "timeseries"
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "Shows the rate of allocations in memory. Sudden increase in allocations would mean increased pressure on Go Garbage Collector and can saturate CPU resources of the application.",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
"axisBorderShow": false,
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
"barWidthFactor": 0.6,
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
"insertNulls": false,
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "line"
}
},
"decimals": 0,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
}
]
},
"unit": "bytes"
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
"y": 87
},
"id": 133,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true
},
"tooltip": {
"hideZeros": false,
"mode": "multi",
"sort": "desc"
}
},
"pluginVersion": "11.5.0",
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"expr": "sum(rate(go_memstats_alloc_bytes_total{job=~\"$job\"}[$__rate_interval])) by (job, instance)",
"format": "time_series",
"interval": "",
"intervalFactor": 2,
"legendFormat": "__auto",
"range": true,
"refId": "A"
}
],
"title": "Memory allocations rate",
"type": "timeseries"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
}
],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"title": "Resource usage",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"type": "row"
},
{
"collapsed": true,
"gridPos": {
"h": 1,
"w": 24,
"x": 0,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"y": 31
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
"id": 71,
"panels": [
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"uid": "$ds"
},
dashboards: update links in various panels * use docs.victoriametrics.com instead of github docs * add links to common terms used in VictoriaMetrics Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-03-04 14:43:31 +00:00
"description": "Shows the rate and total number of new series created over last 24h.\n\nHigh [churn rate](https://docs.victoriametrics.com/faq/#what-is-high-churn-rate) tightly connected with database performance and may result in unexpected OOM's or slow queries. It is recommended to always keep an eye on this metric to avoid unexpected [cardinality](https://docs.victoriametrics.com/keyconcepts/#cardinality) \"explosions\".\n\nThe higher churn rate is, the more resources required to handle it. Consider to keep the churn rate as low as possible.\n\nGood references to read:\n* https://www.robustperception.io/cardinality-is-key\n* https://www.robustperception.io/using-tsdb-analyze-to-investigate-churn-and-cardinality",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"unit": "short"
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
},
"overrides": []
},
"gridPos": {
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"h": 8,
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 249
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"id": 66,
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
}
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"targets": [
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"uid": "$ds"
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(rate(vm_new_timeseries_created_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance)",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"interval": "",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - churn rate",
"range": true,
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"refId": "A"
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(increase(vm_new_timeseries_created_total{job=~\"$job\", instance=~\"$instance\"}[24h])) by (instance)",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"interval": "",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - new series over 24h",
"range": true,
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"refId": "B"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Churn rate",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards: improve wording for SlowInserts panel info Signed-off-by: hagen1778 <roman@victoriametrics.com>
2025-01-30 13:20:28 +00:00
"description": "The percentage of [slow inserts](https://docs.victoriametrics.com/faq/#what-is-a-slow-insert) compared to the total ingestion rate. \\n\\nThe lower the better. \\n\\nIn short, slow insert is a cache miss. There are following reasons for slow inserts to go up: \\n* Ingestion of completely new, not seen before time series;\\n* Not enough memory to maintain big enough caches for the current workload.\\n\\nIf percentage remains high (>10%) during extended periods of time, then it is likely more RAM is needed for optimal handling of the current number of [active time series](https://docs.victoriametrics.com/faq/#what-is-an-active-time-series). \\n\\nSee [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3976#issuecomment-1476883183) for details.",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "line+area"
}
},
"decimals": 2,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "transparent"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 0.1
}
]
},
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"unit": "percentunit"
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
},
"overrides": []
},
"gridPos": {
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"h": 8,
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"w": 12,
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 249
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"id": 68,
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "max(\n rate(vm_slow_row_inserts_total{job=~\"$job\"}[$__rate_interval]) \n / rate(vm_rows_added_to_storage_total{job=~\"$job\"}[$__rate_interval])\n) by (instance)",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"format": "time_series",
"hide": false,
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"interval": "",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Slow inserts %",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "Merge assist happens when storage can't keep up with merging parts. This is usually a sign of overload for storage.",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "bars",
"fillOpacity": 100,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"unit": "short"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 257
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"id": 116,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"targets": [
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
{
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"exemplar": false,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(increase(vm_assisted_merges_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by(instance, type) > 0",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"format": "time_series",
"interval": "5m",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{type}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
"refId": "A"
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Assisted merges",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "Slow queries rate according to `search.logSlowQueryDuration` flag, which is `5s` by default.",
dashboard: set Y-min to zero for most of panels in cluster dashboard (#737) Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-09-02 12:15:13 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"unit": "short"
dashboard: set Y-min to zero for most of panels in cluster dashboard (#737) Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-09-02 12:15:13 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 257
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 60,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(rate(vm_slow_queries_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance)",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"format": "time_series",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"hide": false,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}}",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Slow queries rate",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "Shows the percentage of used cache size from the allowed size by type. \nValues close to 100% show the maximum potential utilization.\nValues close to 0% show that cache is underutilized.",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"unit": "percentunit"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"overrides": []
},
"gridPos": {
"h": 9,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 265
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"id": 90,
"options": {
"legend": {
"calcs": [
"lastNotNull",
"mean",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"targets": [
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"exemplar": false,
"expr": "vm_cache_size_bytes{job=~\"$job\", instance=~\"$instance\"} / vm_cache_size_max_bytes{job=~\"$job\", instance=~\"$instance\"}",
"interval": "",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{type}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
"refId": "A"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Cache usage % by type",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "Shows cache miss ratio. Lower is better.",
dashboard: set Y-min to zero for most of panels in cluster dashboard (#737) Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-09-02 12:15:13 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"max": 1,
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"unit": "percentunit"
dashboard: set Y-min to zero for most of panels in cluster dashboard (#737) Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-09-02 12:15:13 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"h": 9,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"w": 12,
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 265
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 118,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
"exemplar": false,
"expr": "(\n rate(vm_cache_misses_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])\n /\n rate(vm_cache_requests_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])\n) > 0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"format": "time_series",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"hide": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{type}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Cache miss ratio",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
{
"datasource": {
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"type": "prometheus",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"uid": "$ds"
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"description": "Shows how many samples were ignored or dropped on insertion due to various reasons:\n* timestamp out of retention period or timestamp in future;\n* invalid metric name;\n* exceeding limit for labels length or number;\n* dropped by [relabeling configuration](https://docs.victoriametrics.com/#relabeling).",
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
"axisBorderShow": false,
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
"insertNulls": false,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"lineInterpolation": "linear",
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 274
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"id": 131,
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"options": {
"legend": {
"calcs": [
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"mean",
"lastNotNull",
"max"
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"mode": "multi",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"sort": "none"
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"exemplar": true,
"expr": "sum(increase(vm_rows_ignored_total{job=~\"$job\", instance=~\"$instance\"}[1h])) by (instance, reason)",
"hide": false,
"interval": "",
"legendFormat": "{{instance}} - {{reason}}",
"range": true,
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"refId": "A"
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"expr": "sum(increase(vm_relabel_metrics_dropped_total{job=~\"$job\", instance=~\"$instance\"}[1h])) by(instance)",
"hide": false,
"instant": false,
"legendFormat": "{{instance}} - relabeling",
"range": true,
"refId": "B"
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
}
],
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"title": "Samples dropped for last 1h",
dashboards: add Restarts panel (#7394) Reopening PR #7373 from a branch in VictoriaMetrics repo in order to enable edits and rebase. - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 683f8c2780fccd9fcc8fae2d2925f3410fc0a9b1)
2024-10-30 15:44:08 +00:00
"type": "timeseries"
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"description": "Shows rate of deduplicated samples during [deduplication](https://docs.victoriametrics.com/#deduplication) or [downsampling](https://docs.victoriametrics.com/#downsampling), according to the configured `-dedup.minScrapeInterval` or `-downsampling.period`.\n\nShould be empty if `-dedup.minScrapeInterval` and `-downsampling.period` isn't set.\n\nDeduplication happens in two places:\n* `type=\"merge\"` - during [background merges](https://docs.victoriametrics.com/#storage). Deduplication during merges is permanent.\n* `type=\"select\"` - during [read queries](https://docs.victoriametrics.com/keyconcepts/#query-data). Deduplication happens in-flight and has no permanent effect.\n\nThe more samples need to be deduplicated, the higher will be resource usage.",
dashboard: set Y-min to zero for most of panels in cluster dashboard (#737) Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-09-02 12:15:13 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
{
"color": "red",
"value": 80
}
]
},
"unit": "short"
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 274
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
"id": 132,
"links": [
{
"targetBlank": true,
"title": "Readonly mode",
"url": "https://docs.victoriametrics.com/cluster-victoriametrics/#readonly-mode"
}
],
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true
},
"tooltip": {
"hideZeros": false,
"mode": "multi",
"sort": "none"
}
},
"pluginVersion": "11.5.0",
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"exemplar": true,
"expr": "sum(rate(vm_deduplicated_samples_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by(instance, type) > 0",
"format": "time_series",
"interval": "",
"intervalFactor": 1,
"legendFormat": "__auto",
"range": true,
"refId": "A"
}
],
"title": "Deduplication rate",
"type": "timeseries"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "Flags explicitly set to non-default values",
"fieldConfig": {
"defaults": {
"color": {
"mode": "thresholds"
},
"custom": {
"align": "auto",
"cellOptions": {
"type": "auto"
},
"inspect": false
},
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
{
"color": "red",
"value": 80
}
]
}
},
"overrides": [
{
"matcher": {
"id": "byName",
"options": "Time"
},
"properties": [
{
"id": "custom.hidden",
"value": true
}
]
},
{
"matcher": {
"id": "byName",
"options": "Value"
},
"properties": [
{
"id": "custom.hidden",
"value": true
}
]
},
{
"matcher": {
"id": "byName",
"options": "job"
},
"properties": [
{
"id": "custom.hidden",
"value": true
}
]
}
]
},
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 282
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
"id": 126,
"options": {
"cellHeight": "sm",
"footer": {
"countRows": false,
"fields": "",
"reducer": [
"sum"
],
"show": false
},
"showHeader": true
},
"pluginVersion": "11.5.0",
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"exemplar": false,
"expr": "sum(flag{is_set=\"true\", job=~\"$job\", instance=~\"$instance\"}) by(job, instance, name, value)",
"format": "table",
"instant": true,
"legendFormat": "__auto",
"range": false,
"refId": "A"
}
],
"title": "Non-default flags",
"type": "table"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "Shows the number of restarts per job. The chart can be useful to identify periodic process restarts and correlate them with potential issues or anomalies. Normally, processes shouldn't restart unless restart was inited by user. The reason of restarts should be figured out by checking the logs of each specific service. ",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
"axisBorderShow": false,
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"axisSoftMin": 0,
"barAlignment": 0,
"barWidthFactor": 0.6,
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
"insertNulls": false,
"lineInterpolation": "stepAfter",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 0,
"links": [],
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
{
"color": "red",
"value": 80
}
]
},
"unit": "none"
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 282
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
"id": 129,
"options": {
"legend": {
"calcs": [
"lastNotNull"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
"hideZeros": false,
"mode": "multi",
"sort": "desc"
}
},
"pluginVersion": "11.5.0",
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"expr": "sum(changes(vm_app_start_timestamp{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval]) > 0) by(job)",
"format": "time_series",
"instant": false,
"legendFormat": "{{job}}",
"refId": "A"
}
],
"title": "Restarts ($job)",
"type": "timeseries"
}
],
"title": "Troubleshooting",
"type": "row"
},
{
"collapsed": true,
"gridPos": {
"h": 1,
"w": 24,
"x": 0,
"y": 32
},
"id": 14,
"panels": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "How many datapoints are inserted into storage per second",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
"axisBorderShow": false,
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
"barWidthFactor": 0.6,
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
"insertNulls": false,
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboard: set Y-min to zero for most of panels in cluster dashboard (#737) Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
2020-09-02 12:15:13 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"w": 12,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 347
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 10,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(rate(vm_rows_inserted_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance, type) > 0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"format": "time_series",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"hide": false,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{type}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Datapoints ingestion rate",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards: mention reserved disk space in descriptions Follow-up after 57ddb5108926279979b721b687817ca772da14de Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-12-03 11:16:36 +00:00
"description": "Shows the approx time needed to reach 100% of disk capacity based on the following params:\n* free disk space (after -storage.minFreeDiskSpaceBytes);\n* row ingestion rate;\n* compression.\n\nNote: this panel doesn't account for deduplication process.",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "s"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 347
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"id": 73,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"min"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"targets": [
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
dashboards: fix query for full ETA vm_free_disk_space_bytes - vm_free_disk_space_limit_bytes (#7355) ### Describe Your Changes Fix https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7334 available disk space should be ``` (vm_free_disk_space_bytes{job=~...} - vm_free_disk_space_limit_bytes{job=~...}) ``` instead of ``` vm_free_disk_space_bytes{job=~...} ``` ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/).
2024-10-25 13:09:14 +00:00
"expr": "(vm_free_disk_space_bytes{job=~\"$job\", instance=~\"$instance\"}-vm_free_disk_space_limit_bytes{job=~\"$job\", instance=~\"$instance\"}) \n/ ignoring(path) (\n rate(vm_rows_added_to_storage_total{job=~\"$job\", instance=~\"$instance\"}[1d]) \n * scalar(\n sum(vm_data_size_bytes{job=~\"$job\", instance=~\"$instance\", type!~\"indexdb.*\"}) \n / sum(vm_rows{job=~\"$job\", instance=~\"$instance\", type!~\"indexdb.*\"})\n )\n )",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"hide": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"intervalFactor": 1,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legendFormat": "{{instance}}",
"range": true,
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Storage full ETA",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards: mention reserved disk space in descriptions Follow-up after 57ddb5108926279979b721b687817ca772da14de Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-12-03 11:16:36 +00:00
"description": "Shows amount of on-disk space occupied by data points and the remaining disk space at `-storageDataPath`. Calculation accounts for -storage.minFreeDiskSpaceBytes",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "bytes"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 355
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"id": 53,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(vm_data_size_bytes{job=~\"$job\", instance=~\"$instance\", type!~\"indexdb.*\"}) by (instance)",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"format": "time_series",
"interval": "",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - Used (datapoints)",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
"refId": "A"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards: fix query for full ETA vm_free_disk_space_bytes - vm_free_disk_space_limit_bytes (#7355) ### Describe Your Changes Fix https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7334 available disk space should be ``` (vm_free_disk_space_bytes{job=~...} - vm_free_disk_space_limit_bytes{job=~...}) ``` instead of ``` vm_free_disk_space_bytes{job=~...} ``` ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/).
2024-10-25 13:09:14 +00:00
"expr": "vm_free_disk_space_bytes{job=~\"$job\", instance=~\"$instance\"} - vm_free_disk_space_limit_bytes{job=~\"$job\", instance=~\"$instance\"}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"format": "time_series",
"interval": "",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - Free",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "B"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(vm_data_size_bytes{job=~\"$job\", instance=~\"$instance\", type=~\"indexdb.*\"}) by (instance)",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"hide": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - Used (index)",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"refId": "C"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Disk space usage - datapoints",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards: fix description about pending datapoints (#7235) See [our playground](https://play-grafana.victoriametrics.com/d/oS7Bi_0Wz_vm/victoriametrics-cluster-vm?orgId=1&var-ds=P996FABE17B5F6D1E&var-job=All&var-job_insert=All&var-job_select=All&var-job_storage=All&var-instance=All) for reference. (cherry picked from commit d3f110373ca5912a1a0c9438212ba72ad08f7300)
2024-10-11 11:47:14 +00:00
"description": "How many datapoints are in RAM queue waiting to be written into storage. The number of pending data points should be in the range from 0 to `3*<ingestion_rate>`, since VictoriaMetrics pushes pending data to persistent storage every two seconds.",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"overrides": [
{
"matcher": {
"id": "byName",
"options": "pending index entries"
},
"properties": [
{
"id": "unit",
"value": "none"
},
{
"id": "decimals",
"value": 3
}
]
}
]
},
"gridPos": {
"h": 8,
"w": 12,
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 355
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"id": 34,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"targets": [
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"expr": "vm_pending_rows{job=~\"$job\", instance=~\"$instance\", type=\"storage\"}",
"format": "time_series",
"hide": false,
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - pending datapoints",
"range": true,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"refId": "A"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"expr": "vm_pending_rows{job=~\"$job\", instance=~\"$instance\", type=\"indexdb\"}",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"hide": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - pending index entries",
"range": true,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"refId": "B"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Pending datapoints",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"description": "Shows how many datapoints are in the storage and what is average disk usage per datapoint.",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"overrides": [
{
"matcher": {
"id": "byName",
"options": "bytes-per-datapoint"
},
"properties": [
{
"id": "unit",
"value": "bytes"
},
{
"id": "decimals",
"value": 2
}
]
}
]
},
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 363
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"id": 30,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(vm_rows{job=~\"$job\", instance=~\"$instance\", type!~\"indexdb.*\"}) by (instance)",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"format": "time_series",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"interval": "",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - total datapoints",
"range": true,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"refId": "A"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(vm_data_size_bytes{job=~\"$job\", instance=~\"$instance\"}) by (instance)\n/ sum(vm_rows{job=~\"$job\", instance=~\"$instance\", type!~\"indexdb.*\"}) by (instance)",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"interval": "",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - bytes-per-datapoint",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
"refId": "B"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Datapoints",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
"uid": "$ds"
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"description": "The max number of data parts of LSM tree across all storage nodes in the last [partition](https://docs.victoriametrics.com/#storage).\nIncrease in number of parts (the hard limit is 512) is an evidence of slow merge performance - check the resource utilization.\n* `indexdb` - inverted index\n* `storage/small` - recently added parts of data ingested into storage (hot data)\n* `storage/big` - small parts gradually merged into bigger parts (cold data)",
dashboards/victoriametrics: update `Concurrent inserts` panel #632 (#645) Panel `Concurrent inserts` was moved to `vminsert` row. Its metrics and description was updated accordingly to #632 issue.
2020-07-22 09:43:23 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboards/victoriametrics: update `Concurrent inserts` panel #632 (#645) Panel `Concurrent inserts` was moved to `vminsert` row. Its metrics and description was updated accordingly to #632 issue.
2020-07-22 09:43:23 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 363
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 36,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
}
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"expr": "sum(vm_parts{job=~\"$job\", instance=~\"$instance\", type=~\"indexdb.*\"}) by (instance, type)",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"format": "time_series",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{type}}",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"expr": "max(vm_last_partition_parts{job=~\"$job\", instance=~\"$instance\"}) by(instance, type)",
"format": "time_series",
"hide": false,
"intervalFactor": 1,
"legendFormat": "{{instance}} - {{type}}",
"range": true,
"refId": "B"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
}
],
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"title": "LSM parts max by type",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
},
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
app/{vminsert,vmagent}: drop time series on exceeding labels limits. Previously, time series with labels exceeding the configured limits were truncated and written to storage, potentially causing data inconsistency. This could lead to collisions between time series and make it difficult to identify the source due to truncated labels. This commit changes the behavior: * Such time series are now rejected outright. * Rejected time series are logged to stdout, and corresponding counters are incremented. * removes `vm_too_long_label_values_total`, `vm_too_long_label_names_total`, `vm_metrics_with_dropped_labels_total` metrics. * adds new values `[too_many_labels,too_long_label_name,too_long_label_value]` to `reason` label of the `vm_rows_ignored_total` metric name related issues: - https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6928 - https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7661
2024-12-10 21:15:38 +00:00
"description": "Shows how many rows were ignored on insertion due to corrupted or out of retention timestamps and how many series were ignored on insertion or during scrape due to too long label names, values and excessive labels count.",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 10,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 371
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"id": 58,
"options": {
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"targets": [
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"exemplar": false,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"expr": "sum(increase(vm_rows_ignored_total{job=~\"$job\", instance=~\"$instance\"}[1h])) by (instance, reason)",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"hide": false,
"interval": "",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - {{reason}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
"refId": "A"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Rows ignored for last 1h",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "The number of on-going merges in storage nodes. It is expected to have high numbers for `storage/small` metric.",
dashboards/victoriametrics: update `Concurrent inserts` panel #632 (#645) Panel `Concurrent inserts` was moved to `vminsert` row. Its metrics and description was updated accordingly to #632 issue.
2020-07-22 09:43:23 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 0,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboards/victoriametrics: update `Concurrent inserts` panel #632 (#645) Panel `Concurrent inserts` was moved to `vminsert` row. Its metrics and description was updated accordingly to #632 issue.
2020-07-22 09:43:23 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 371
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 62,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(vm_active_merges{job=~\"$job\", instance=~\"$instance\"}) by(instance, type)",
"legendFormat": "{{instance}} - {{type}}",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Active merges",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "Shows how many ongoing insertions (not API /write calls) on disk are taking place, where:\n* `max` - equal to number of CPUs;\n* `current` - current number of goroutines busy with inserting rows into underlying storage.\n\nEvery successful API /write call results into flush on disk. However, these two actions are separated and controlled via different concurrency limiters. The `max` on this panel can't be changed and always equal to number of CPUs. \n\nWhen `current` hits `max` constantly, it means storage is overloaded and requires more CPU.\n\n",
dashboards/victoriametrics: update `Concurrent inserts` panel #632 (#645) Panel `Concurrent inserts` was moved to `vminsert` row. Its metrics and description was updated accordingly to #632 issue.
2020-07-22 09:43:23 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 0,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboards/victoriametrics: update `Concurrent inserts` panel #632 (#645) Panel `Concurrent inserts` was moved to `vminsert` row. Its metrics and description was updated accordingly to #632 issue.
2020-07-22 09:43:23 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"overrides": [
{
"matcher": {
"id": "byName",
"options": "max"
},
"properties": [
{
"id": "color",
"value": {
"fixedColor": "#C4162A",
"mode": "fixed"
}
}
]
}
]
dashboards/victoriametrics: update `Concurrent inserts` panel #632 (#645) Panel `Concurrent inserts` was moved to `vminsert` row. Its metrics and description was updated accordingly to #632 issue.
2020-07-22 09:43:23 +00:00
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 379
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 59,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
}
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
lib/writeconcurrencylimiter: improve the logic behind -maxConcurrentInserts limit Previously the -maxConcurrentInserts was limiting the number of established client connections, which write data to VictoriaMetrics. Some of these connections could be idle. Such connections do not consume big amounts of CPU and RAM, so there is a little sense in limiting the number of such connections. So now the -maxConcurrentInserts command-line option limits the number of concurrently executed insert requests, not including idle connections. It is recommended removing -maxConcurrentInserts command-line option, since the default value for this option should work good for most cases.
2023-01-07 02:59:39 +00:00
"expr": "max_over_time(vm_concurrent_insert_capacity{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"format": "time_series",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"interval": "",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - max",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(vm_concurrent_insert_current{job=~\"$job\", instance=~\"$instance\"}) by (instance)",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"format": "time_series",
"intervalFactor": 1,
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"legendFormat": "{{instance}} - current",
"range": true,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"refId": "B"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Concurrent flushes on disk",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "The number of rows merged per second by storage nodes.",
dashboards/victoriametrics: update `Concurrent inserts` panel #632 (#645) Panel `Concurrent inserts` was moved to `vminsert` row. Its metrics and description was updated accordingly to #632 issue.
2020-07-22 09:43:23 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 0,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboards/victoriametrics: update `Concurrent inserts` panel #632 (#645) Panel `Concurrent inserts` was moved to `vminsert` row. Its metrics and description was updated accordingly to #632 issue.
2020-07-22 09:43:23 +00:00
},
"overrides": []
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 379
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 64,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "none"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"editorMode": "code",
"expr": "sum(rate(vm_rows_merged_total{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by(instance, type)",
"legendFormat": "{{instance}} - {{type}}",
"range": true,
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Merge speed",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
dashboards/victoriametrics: update `Concurrent inserts` panel #632 (#645) Panel `Concurrent inserts` was moved to `vminsert` row. Its metrics and description was updated accordingly to #632 issue.
2020-07-22 09:43:23 +00:00
},
Cluster dashboard update (#1594) * dashboards: sync `vmagent` updates from master branch * dashboards: add new `Storage connection saturation` panel for cluster dashboard * dashboards: add new cluster alert for corresponding `Storage connection saturation` panel
2021-09-01 14:05:17 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"description": "99th percentile of number of series read per query.",
Cluster dashboard update (#1594) * dashboards: sync `vmagent` updates from master branch * dashboards: add new `Storage connection saturation` panel for cluster dashboard * dashboards: add new cluster alert for corresponding `Storage connection saturation` panel
2021-09-01 14:05:17 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 2,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
Cluster dashboard update (#1594) * dashboards: sync `vmagent` updates from master branch * dashboards: add new `Storage connection saturation` panel for cluster dashboard * dashboards: add new cluster alert for corresponding `Storage connection saturation` panel
2021-09-01 14:05:17 +00:00
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 387
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
"id": 99,
Cluster dashboard update (#1594) * dashboards: sync `vmagent` updates from master branch * dashboards: add new `Storage connection saturation` panel for cluster dashboard * dashboards: add new cluster alert for corresponding `Storage connection saturation` panel
2021-09-01 14:05:17 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard update (#1594) * dashboards: sync `vmagent` updates from master branch * dashboards: add new `Storage connection saturation` panel for cluster dashboard * dashboards: add new cluster alert for corresponding `Storage connection saturation` panel
2021-09-01 14:05:17 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"editorMode": "code",
"expr": "histogram_quantile(0.99, sum(rate(vm_series_read_per_query_bucket{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance, vmrange))",
Cluster dashboard update (#1594) * dashboards: sync `vmagent` updates from master branch * dashboards: add new `Storage connection saturation` panel for cluster dashboard * dashboards: add new cluster alert for corresponding `Storage connection saturation` panel
2021-09-01 14:05:17 +00:00
"format": "time_series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "",
"intervalFactor": 1,
"legendFormat": "{{instance}}",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"range": true,
Cluster dashboard update (#1594) * dashboards: sync `vmagent` updates from master branch * dashboards: add new `Storage connection saturation` panel for cluster dashboard * dashboards: add new cluster alert for corresponding `Storage connection saturation` panel
2021-09-01 14:05:17 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Series read per query",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
Cluster dashboard update (#1594) * dashboards: sync `vmagent` updates from master branch * dashboards: add new `Storage connection saturation` panel for cluster dashboard * dashboards: add new cluster alert for corresponding `Storage connection saturation` panel
2021-09-01 14:05:17 +00:00
},
Cluster dashboard (#931) * dashboard: add `Storage full ETA` panel Backport of https://github.com/VictoriaMetrics/VictoriaMetrics/pull/858 * dashboard: add `Storage reachability` panel
2020-11-30 09:30:11 +00:00
{
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
dashboards: update links in various panels * use docs.victoriametrics.com instead of github docs * add links to common terms used in VictoriaMetrics Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-03-04 14:43:31 +00:00
"description": "99th percentile of number of [data samples](https://docs.victoriametrics.com/keyconcepts/#raw-samples) read per queried series.",
Cluster dashboard (#931) * dashboard: add `Storage full ETA` panel Backport of https://github.com/VictoriaMetrics/VictoriaMetrics/pull/858 * dashboard: add `Storage reachability` panel
2020-11-30 09:30:11 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 2,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
Cluster dashboard (#931) * dashboard: add `Storage full ETA` panel Backport of https://github.com/VictoriaMetrics/VictoriaMetrics/pull/858 * dashboard: add `Storage reachability` panel
2020-11-30 09:30:11 +00:00
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 387
Cluster dashboard (#931) * dashboard: add `Storage full ETA` panel Backport of https://github.com/VictoriaMetrics/VictoriaMetrics/pull/858 * dashboard: add `Storage reachability` panel
2020-11-30 09:30:11 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 103,
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"targets": [
{
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add `Cache usage %` panel to Caches row (#2960) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2941 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-08-08 09:45:17 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"expr": "histogram_quantile(0.99, sum(rate(vm_rows_read_per_series_bucket{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance, vmrange))",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"format": "time_series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "",
"intervalFactor": 1,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"legendFormat": "{{instance}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Datapoints read per series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"uid": "$ds"
},
dashboards: update links in various panels * use docs.victoriametrics.com instead of github docs * add links to common terms used in VictoriaMetrics Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-03-04 14:43:31 +00:00
"description": "99th percentile of number of [data samples](https://docs.victoriametrics.com/keyconcepts/#raw-samples) read per query.",
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 2,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
},
"overrides": []
},
"gridPos": {
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"h": 8,
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
"w": 12,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 395
dashboards: add cpu usage panels per each component type (#2723) The change adds extra panel per each component, showing the amount of used CPU cores and the limit (summary of all instances). https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2696 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-06-16 17:49:55 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 122,
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
Cluster dashboard (#931) * dashboard: add `Storage full ETA` panel Backport of https://github.com/VictoriaMetrics/VictoriaMetrics/pull/858 * dashboard: add `Storage reachability` panel
2020-11-30 09:30:11 +00:00
"targets": [
{
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"uid": "$ds"
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"editorMode": "code",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"expr": "histogram_quantile(0.99, sum(rate(vm_rows_read_per_query_bucket{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance, vmrange))",
Cluster dashboard (#931) * dashboard: add `Storage full ETA` panel Backport of https://github.com/VictoriaMetrics/VictoriaMetrics/pull/858 * dashboard: add `Storage reachability` panel
2020-11-30 09:30:11 +00:00
"format": "time_series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "",
Cluster dashboard (#931) * dashboard: add `Storage full ETA` panel Backport of https://github.com/VictoriaMetrics/VictoriaMetrics/pull/858 * dashboard: add `Storage reachability` panel
2020-11-30 09:30:11 +00:00
"intervalFactor": 1,
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"legendFormat": "{{instance}}",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"range": true,
Cluster dashboard (#931) * dashboard: add `Storage full ETA` panel Backport of https://github.com/VictoriaMetrics/VictoriaMetrics/pull/858 * dashboard: add `Storage reachability` panel
2020-11-30 09:30:11 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Datapoints read per query",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
},
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"uid": "$ds"
},
all: replace old https://docs.victoriametrics.com/MetricsQL.html url with the new one - https://docs.victoriametrics.com/metricsql/
2024-04-18 00:14:53 +00:00
"description": "99th percentile of number of [data samples](https://docs.victoriametrics.com/keyconcepts/#raw-samples) scanner per query.\n\nThis number can exceed number of RowsReadPerQuery if `step` query arg passed to [/api/v1/query_range](https://prometheus.io/docs/prometheus/latest/querying/api/#range-queries) is smaller than the lookbehind window set in square brackets of [rollup function](https://docs.victoriametrics.com/metricsql/#rollup-functions). For example, if `increase(some_metric[1h])` is executed with the `step=5m`, then the same [data samples](https://docs.victoriametrics.com/keyconcepts/#raw-samples) on a hour time range are scanned `1h/5m=12` times. See [this article](https://valyala.medium.com/how-to-optimize-promql-and-metricsql-queries-85a1b75bf986) for details.",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"fieldConfig": {
"defaults": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"color": {
"mode": "palette-classic"
},
"custom": {
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"axisBorderShow": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"barWidthFactor": 0.6,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"insertNulls": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"decimals": 2,
"links": [],
"mappings": [],
"min": 0,
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
},
{
"color": "red",
"value": 80
}
]
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"unit": "short"
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
},
"overrides": []
},
"gridPos": {
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"h": 8,
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"w": 12,
"x": 12,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 395
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
},
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"id": 105,
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"options": {
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legend": {
"calcs": [
"mean",
"lastNotNull",
"max"
],
"displayMode": "table",
"placement": "bottom",
"showLegend": true,
"sortBy": "Last *",
"sortDesc": true
},
"tooltip": {
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"hideZeros": false,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"mode": "multi",
"sort": "desc"
}
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"pluginVersion": "11.5.0",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"targets": [
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"uid": "$ds"
},
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"editorMode": "code",
"expr": "histogram_quantile(0.99, sum(rate(vm_rows_scanned_per_query_bucket{job=~\"$job\", instance=~\"$instance\"}[$__rate_interval])) by (instance, vmrange))",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"format": "time_series",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"interval": "",
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"intervalFactor": 1,
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"legendFormat": "{{instance}}",
Dashboard upd (#4438) dashboards: update dashboard for single-node version * add anonymous mem usage panel; * add syscall rate panel; * add location to logs panel; * update legend for panels to reflect instance name; * update queries to aggregate per instance. dashboards: update dashboard for cluster version * add syscall rate panel; * add drilldown to logs panel. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-06-12 13:58:47 +00:00
"range": true,
dashboards: update cluster dashboard (#2773) * dashboards: update cluster dashboard * add assisted merges panel https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2754 * add mem panel per each component * remove lines filling for some panels for clarity Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update dashboards/victoriametrics.json
2022-06-23 07:46:28 +00:00
"refId": "A"
}
],
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"title": "Datapoints scanned per query",
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"type": "timeseries"
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
{
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "$ds"
},
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"description": "Shows number of existing [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots).\n\nRecently made snapshots do not occupy disk space. But with time, as snapshots become older, they start to occupy more and more disk space.\n\nIt is recommended deleting old snapshots when they are no longer needed to free up disk space.",
"fieldConfig": {
"defaults": {
"color": {
"mode": "palette-classic"
},
"custom": {
"axisBorderShow": false,
"axisCenteredZero": false,
"axisColorMode": "text",
"axisLabel": "",
"axisPlacement": "auto",
"barAlignment": 0,
"barWidthFactor": 0.6,
"drawStyle": "line",
"fillOpacity": 0,
"gradientMode": "none",
"hideFrom": {
"legend": false,
"tooltip": false,
"viz": false
},
"insertNulls": false,
"lineInterpolation": "linear",
"lineWidth": 1,
"pointSize": 5,
"scaleDistribution": {
"type": "linear"
},
"showPoints": "never",
"spanNulls": false,
"stacking": {
"group": "A",
"mode": "none"
},
"thresholdsStyle": {
"mode": "off"
}
},
"mappings": [],
"thresholds": {
"mode": "absolute",
"steps": [
{
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"color": "green"
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
{
"color": "red",
"value": 80
}
]
},
"unit": "short"
},
"overrides": []
},
"gridPos": {
"h": 8,
"w": 12,
"x": 0,
dashboards: add `Memory allocations rate` to ResourceUsage tab (#8508) This panel should have help us to identify https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501 during release checks. While we already track the GC pressure, its value is relative and change wasn't noticeable for the workloads that we observed. The absolute values of allocations rate could have helped to see the anomaly. ### 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 [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3511e2e6af6b6822e5b4b05a06828eb0a5d58a19)
2025-03-17 15:42:53 +00:00
"y": 403
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
},
"id": 130,
"options": {
"legend": {
"calcs": [],
"displayMode": "list",
"placement": "bottom",
"showLegend": true
},
"tooltip": {
"hideZeros": false,
"mode": "multi",
"sort": "desc"
}
},
"pluginVersion": "11.5.0",
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "$ds"
},
"editorMode": "code",
"exemplar": true,
"expr": "vm_snapshots{job=~\"$job\", instance=~\"$instance\"}",
"interval": "",
"legendFormat": "{{instance}}",
"range": true,
"refId": "A"
}
],
"title": "Number of snapshots",
"type": "timeseries"
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
}
],
dashboards: update VM single dash (#3400) The change list is the following: * bump Grafana version to 9.2.6; * replace old "Graph" panel with "TimeSeries" panel; * show % usage of Mem and CPU additionally to of absolute values; * `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`; * add Annotations for Alert triggers. Not all alerts are supposed to be displayed on the dashboard, but only those with label `show_at: dashboard`. See `alerts.yml` change. Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-29 18:28:22 +00:00
"title": "Storage",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"type": "row"
}
],
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"preload": false,
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"refresh": "",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"schemaVersion": 40,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"tags": [
"victoriametrics",
"vmsingle"
],
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"templating": {
"list": [
{
"current": {
Update dashboard according to new Grafana version and some metric renames. (#392) The list of changes is following: * fix Uptime panel column styles according to changes introduced in 6.7 Grafana version * fix panel `vminsert/Rows per insert` due to metric rename - see #336 * change default datasource to VictoriaMetrics since dashboard now uses MetricsQL for `vminsert/Rows per insert` panel
2020-03-27 23:17:38 +00:00
"text": "VictoriaMetrics",
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"value": "P4169E866C3094E38"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
"includeAll": false,
"name": "ds",
"options": [],
"query": "prometheus",
"refresh": 1,
"regex": "",
"type": "datasource"
},
{
prepare dashboard for external sharing (#231)
2019-11-11 22:23:24 +00:00
"current": {},
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"definition": "label_values(vm_app_version{version=~\"victoria-metrics-.*\"}, job)",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"includeAll": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"name": "job",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"options": [],
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"query": {
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"query": "label_values(vm_app_version{version=~\"victoria-metrics-.*\"}, job)",
"refId": "VictoriaMetrics-job-Variable-Query"
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refresh": 1,
"regex": "",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"type": "query"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
prepare dashboard for external sharing (#231)
2019-11-11 22:23:24 +00:00
"current": {},
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"definition": "label_values(vm_app_version{job=~\"$job\", instance=~\"$instance\"}, version)",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"hide": 2,
"includeAll": false,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"name": "version",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"options": [],
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"query": {
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"query": "label_values(vm_app_version{job=~\"$job\", instance=~\"$instance\"}, version)",
"refId": "VictoriaMetrics-version-Variable-Query"
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refresh": 1,
deployment/dashboards: properly show version for non-stable docker images (#6150) re: .*-(?:tags|heads)-(.*)-(?:0|dirty)-.* cases: victoria-metrics-20240419-160209-heads-enterprise-single-node-0-g08f933ab0c enterprise-single-node victoria-metrics-20240201-133950-tags-v1.97.1-enterprise-0-g760a8733b v1.97.1-enterprise victoria-metrics-20240419-160209-heads-rotation-part-2-0-ge2367b6d1-dirty-848b54cd rotation-part-2-0-ge2367b6d1 victoria-metrics-20240419-160209-heads-lts-1.93-enterprise-search-contention-0-g30ef4aad21-amd64 lts-1.93-enterprise-search-contention victoria-metrics-20240425-150852-tags-v1.101.0-enterprise-0-g718138c64 v1.101.0-enterprise Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: Dzmitry Lazerka <dlazerka@gmail.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 564463259a1f7c8aec3c17e77d8c9dcea198e787)
2024-04-29 09:11:28 +00:00
"regex": "/.*-(?:tags|heads)-(.*)-(?:0|dirty)-.*/",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"sort": 2,
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"type": "query"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
{
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"allValue": ".*",
prepare dashboard for external sharing (#231)
2019-11-11 22:23:24 +00:00
"current": {},
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"datasource": {
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"type": "prometheus",
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"uid": "$ds"
},
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"definition": "label_values(vm_app_version{job=~\"$job\"}, instance)",
dashboards/victoria-metrics-single: allow selecting multiple instance values (#5870) Allowing to select multiple instance IPs makes it much easier to view metrics for longer periods of time in dynamic environments such as Kubernetes. In k8s update will also cause IP to change making it harder to use dashboard to check the status. See: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5869 --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 6b493582da03c56ace01ed05e7c1d178657ab1bf)
2024-04-29 08:34:36 +00:00
"includeAll": true,
"multi": true,
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"name": "instance",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"options": [],
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
"query": {
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"query": "label_values(vm_app_version{job=~\"$job\"}, instance)",
"refId": "VictoriaMetrics-instance-Variable-Query"
Cluster dashboard update (#1185) * dashboard: change FreeDiskSpace panel to show percentage of used space instead * dashboard: disable area fill for Cache hit ratio * dashboard: minor display updates * dashboard: add panel `Concurrent flushes on disk` * dashboard: add `Rows ignored` panel * dashboard: update ChurnRate panel with proper description and additional query over 24h time window
2021-04-05 19:28:02 +00:00
},
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"refresh": 1,
"regex": "",
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"type": "query"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
},
dashboards: add adhoc filter to dasbhoard variables The adhoc filter allows to quickly apply global filters without modifying the panels. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-04-22 14:25:53 +00:00
{
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
"baseFilters": [],
dashboards: add adhoc filter to dasbhoard variables The adhoc filter allows to quickly apply global filters without modifying the panels. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-04-22 14:25:53 +00:00
"datasource": {
"type": "prometheus",
Update `datasource` entries consistently contain type `prometheus` and uid `$ds`. (#3393) Co-authored-by: Timour I. Bakeev <tbakeev@ripe.net>
2022-11-28 07:37:39 +00:00
"uid": "$ds"
dashboards: add adhoc filter to dasbhoard variables The adhoc filter allows to quickly apply global filters without modifying the panels. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-04-22 14:25:53 +00:00
},
"filters": [],
"name": "adhoc",
"type": "adhoc"
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
}
]
},
"time": {
dashboards: update to grafana/grafana:10.3.1 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-02 14:41:08 +00:00
"from": "now-3h",
Cluster dashboard (#222) * add dashboard for cluster version * fix queries and panels * review fixes * use resident memory for memory usage panel * fix job selectors
2019-11-07 10:09:27 +00:00
"to": "now"
},
"timepicker": {
"refresh_intervals": [
"10s",
"30s",
"1m",
"5m",
"15m",
"30m",
"1h",
"2h",
"1d"
]
},
"timezone": "",
deployment/dashboards: change title `VictoriaMetrics` to `VictoriaMetrics - single-node` The new title should provide better understanding of this dashboard purpose. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-01-16 19:39:52 +00:00
"title": "VictoriaMetrics - single-node",
moved cluster dashboard to master (#3074) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.
2022-09-06 14:19:43 +00:00
"uid": "wNf0q_kZk",
dashboards: add `Network Usage` panel to `Resource Usage` row https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4478 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 8606b48ce5df3f4e1a2edef1acae8e98d0189d00)
2024-04-29 09:54:17 +00:00
"version": 1,
Dashboards cluster (#1983) * dashboards/cluster: add panels for vmstorage in read-only mode vmstorage readonly status panel was addded to "vmstorage" row. A one more panel for showing vminsert->vmstorage readonly status was added to troubleshooting row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Cache usage" panel The new panel supposed to show the % of the used cache compared to allowed size by type. It should help to determine underutilized types of caches. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: add "Merges deferred" panel The new panel supposed to show if there were deferred merges due to insufficient disk space. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: update Network panel for vminsert * delete bytes_written query, since in most cases it is insiginificant * change display type to Stack Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/cluster: bump version requirement Signed-off-by: hagen1778 <roman@victoriametrics.com>
2021-12-20 15:32:05 +00:00
"weekStart": ""
dashboards: add new panels to VictoriaMetrics dashboards (#8369) * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Deduplication rate` that shows how many samples are [deduplicated](https://docs.victoriametrics.com/#deduplication) during merges or read queries by VictoriaMetrics components. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Number of snapshots` that shows the max number of [snapshots](https://docs.victoriametrics.com/#how-to-work-with-snapshots) across vmstorage nodes. This panel should help in disk usage [troubleshooting](https://docs.victoriametrics.com/#snapshot-troubleshooting). * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): account for samples dropped according to [relabeling config](https://docs.victoriametrics.com/#relabeling) in `Samples dropped for last 1h` panel. * FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229) and [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): show number of parts in the last partition on `LSM parts max by type` panel. Before, the resulting graph could be skewed by the max number of parts across all partitions. Displaying parts for the latest partition is the correct way to show if storage is currently impacted by merge delays. * FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partial query results` that shows the number of served [partial responses](https://docs.victoriametrics.com/cluster-victoriametrics/#cluster-availability) by vmselects. ------------- Sorry, git diff is a mess. Dashboards switched to Grafana 11 and it broke consistency of changes. --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cddccfde57768b5d0dd851650f6b103ddbc6011b)
2025-02-25 08:25:34 +00:00
}
Reference in a new issue Copy permalink