diff --git a/documentation/operator-guide/management.rst b/documentation/operator-guide/management.rst
index 8d384438d05b764e7ea5237a1d2e4a60fbe4feac..3125157ca58c1d4e4201841b22e7545aa5d265bd 100644
--- a/documentation/operator-guide/management.rst
+++ b/documentation/operator-guide/management.rst
@@ -59,4 +59,19 @@ A new deployment of the stack will use the updated configuration. The above
 mentioned process necessarily involves a certain service downtime between
 shutting down of the stack and new deployment.
 
+Cleaning up
+-----------
+Current configuration of the services does not have any log rotation set up, which means that service logs can grow significantly over time, if left not maintained and set on verbose logging levels. In order to delete logs older than 7 days from a single node, a following command can be run
+
+.. code-block:: bash
+
+    journalctl --vacuum-time=7d
+
+Additionally in order to delete older logs from docker containers present on a node, keeping only a certain number of newest rows, a following command can be run.
+
+.. code-block:: bash
+
+    truncate -s <number rows to keep> $(docker inspect -f '{{.LogPath}}' $container 2> /dev/null)
+
+
 The final section :ref:`ingestion` explains how to get data into the VS.