From 3569352fe05a8255901a05631fd98b627f60bd09 Mon Sep 17 00:00:00 2001 From: Roman Khavronenko Date: Tue, 15 Feb 2022 21:57:21 +0200 Subject: [PATCH] dashboards: update the threshold for slow inserts % on the dashboard (#2198) Signed-off-by: hagen1778 --- dashboards/victoriametrics.json | 30 ++++++++++++++++++++---------- 1 file changed, 20 insertions(+), 10 deletions(-) diff --git a/dashboards/victoriametrics.json b/dashboards/victoriametrics.json index de71f1494..b322a3db3 100644 --- a/dashboards/victoriametrics.json +++ b/dashboards/victoriametrics.json @@ -57,7 +57,7 @@ "fiscalYearStartMonth": 0, "graphTooltip": 0, "id": null, - "iteration": 1644910726761, + "iteration": 1644936794057, "links": [ { "icon": "doc", @@ -2787,7 +2787,7 @@ "alertThreshold": true }, "percentage": false, - "pluginVersion": "8.3.2", + "pluginVersion": "8.3.5", "pointradius": 2, "points": false, "renderer": "flot", @@ -2892,7 +2892,7 @@ "alertThreshold": true }, "percentage": false, - "pluginVersion": "8.3.2", + "pluginVersion": "8.3.5", "pointradius": 2, "points": false, "renderer": "flot", @@ -2949,7 +2949,7 @@ "datasource": { "uid": "$ds" }, - "description": "The percentage of slow inserts comparing to total insertion rate during the last 5 minutes. \n\nThe less value is better. If percentage remains high (>50%) during extended periods of time, then it is likely more RAM is needed for optimal handling of the current number of active time series. \n\nIn general, VictoriaMetrics requires ~1KB or RAM per active time series, so it should be easy calculating the required amounts of RAM for the current workload according to capacity planning docs. But the resulting number may be far from the real number because the required amounts of memory depends on may other factors such as the number of labels per time series and the length of label values.", + "description": "The percentage of slow inserts comparing to total insertion rate during the last 5 minutes. \n\nThe less value is better. If 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. \n\nIn general, VictoriaMetrics requires ~1KB or RAM per active time series, so it should be easy calculating the required amounts of RAM for the current workload according to capacity planning docs. But the resulting number may be far from the real number because the required amounts of memory depends on may other factors such as the number of labels per time series and the length of label values.", "fieldConfig": { "defaults": { "links": [] @@ -2985,7 +2985,7 @@ "alertThreshold": true }, "percentage": false, - "pluginVersion": "8.3.2", + "pluginVersion": "8.3.5", "pointradius": 2, "points": false, "renderer": "flot", @@ -3001,7 +3001,17 @@ "refId": "A" } ], - "thresholds": [], + "thresholds": [ + { + "$$hashKey": "object:72", + "colorMode": "critical", + "fill": true, + "line": true, + "op": "gt", + "value": 0.1, + "yaxis": "left" + } + ], "timeRegions": [], "title": "Slow inserts", "tooltip": { @@ -3079,7 +3089,7 @@ "alertThreshold": true }, "percentage": false, - "pluginVersion": "8.3.2", + "pluginVersion": "8.3.5", "pointradius": 2, "points": false, "renderer": "flot", @@ -3186,7 +3196,7 @@ "alertThreshold": true }, "percentage": false, - "pluginVersion": "8.3.2", + "pluginVersion": "8.3.5", "pointradius": 1, "points": false, "renderer": "flot", @@ -3282,7 +3292,7 @@ "alertThreshold": true }, "percentage": false, - "pluginVersion": "8.3.2", + "pluginVersion": "8.3.5", "pointradius": 2, "points": false, "renderer": "flot", @@ -3387,7 +3397,7 @@ "alertThreshold": true }, "percentage": false, - "pluginVersion": "8.3.2", + "pluginVersion": "8.3.5", "pointradius": 1, "points": false, "renderer": "flot",