diff --git a/docs/stream-aggregation-check-total-reset.png b/docs/stream-aggregation-check-total-reset.png
new file mode 100644
index 0000000000..bc577f7c4e
Binary files /dev/null and b/docs/stream-aggregation-check-total-reset.png differ
diff --git a/docs/stream-aggregation.md b/docs/stream-aggregation.md
index 1ad21511e3..6067b5d7bc 100644
--- a/docs/stream-aggregation.md
+++ b/docs/stream-aggregation.md
@@ -355,6 +355,20 @@ For example, see below time series produced by config with aggregation interval
 
 <img alt="total aggregation" src="stream-aggregation-check-total.png">
 
+`total` is not affected by [counter resets](https://docs.victoriametrics.com/keyConcepts.html#counter) - 
+it continues to increase monotonically with respect to the previous value.
+The counters are most often reset when the application is restarted.
+
+For example: 
+
+<img alt="total aggregation counter reset" src="stream-aggregation-check-total-reset.png">
+
+The same behavior will occur when creating or deleting new series in an aggregation group -
+`total` will increase monotonically considering the values of the series set. 
+
+An example of changing a set of series can be restarting a pod in the Kubernetes.
+This changes a label with pod's name in the series, but `total` account for such a scenario and do not reset the state of aggregated metric.
+
 ### increase
 
 `increase` returns the increase of input [counters](https://docs.victoriametrics.com/keyConcepts.html#counter).