Merge remote-tracking branch 'origin/main'

Author: bvt123

content/en/altinity-kb-setup-and-maintenance/altinity-kb-system-tables-eat-my-disk.md

@@ -47,23 +47,21 @@ $ cat /etc/clickhouse-server/config.d/z_log_disable.xml
 </clickhouse>
 ```
 
-**We do not recommend removing `query_log` and `query_thread_log` as queries' (they have very useful information for debugging), and logging can be easily turned off without a restart through user profiles:**
+Hint: `z_log_disable.xml` is named with **z_** in the beginning, it means this config will be applied the last and will override all other config files with these sections (config are applied in alphabetical order).
+
+**We do not recommend removing `query_log` as it has very useful information for debugging, and logging can be easily turned off without a restart through user profiles:**
 
 ```markup
 $ cat /etc/clickhouse-server/users.d/z_log_queries.xml
 <clickhouse>
     <profiles>
         <default>
             <log_queries>0</log_queries> <!-- normally it's better to keep it turned on! -->
-            <log_query_threads>0</log_query_threads>
-            <log_processors_profiles>0</log_processors_profiles>
         </default>
     </profiles>
 </clickhouse>
 ```
 
-Hint: `z_log_disable.xml` is named with **z_** in the beginning, it means this config will be applied the last and will override all other config files with these sections (config are applied in alphabetical order).
-
 You can also configure these settings to reduce the amount of data in the `system.query_log` table:
 
 ```markup
@@ -77,6 +75,27 @@ log_query_settings                | 1           | Log query settings into the qu
 log_queries_probability           | 1           | Log queries with the specified probabality.
 ```
 
+The other system log tables that can be disabled in profiles are:
+* query_views_log
+* query_thread_log
+* processors_profile_log
+* query_metric_log
+* trace_log (https://clickhouse.com/docs/operations/system-tables/trace_log)
+
+```markup
+$ cat /etc/clickhouse-server/users.d/z_log_tables.xml
+<clickhouse>
+    <profiles>
+        <default>
+            <log_query_views>0</log_query_views>
+            <log_query_threads>0</log_query_threads>
+            <log_processors_profiles>0</log_processors_profiles>
+            <query_metric_log_interval>0</query_metric_log_interval>
+        </default>
+    </profiles>
+</clickhouse>
+```
+
 ## You can configure TTL
 
 Example for `query_log`. It drops partitions with data older than 14 days:
@@ -133,25 +152,3 @@ $ cat /etc/clickhouse-server/config.d/query_log_ttl.xml
 💡 For the [clickhouse-operator](https://github.com/Altinity/clickhouse-operator/blob/master/README.md), the above method of using only the `<engine>` tag without `<ttl>` or `<partition>` is recommended, because of possible configuration clashes.
 
 After that you need to restart ClickHouse and *if using old clickhouse versions like 20 or less*, drop or rename the existing system.query_log table and then CH creates a new table with these settings. This is automatically done in newer versions 21+.
-
-
-## You can disable logging on a session level or in user’s profile (for all or specific users)
-
-But only for logs generated on session level (`query_log` / `query_thread_log`)
-
-In this case a restart is not needed.
-
-Let’s disable query logging for all users (profile = default, all other profiles inherit it).
-
-```markup
-cat /etc/clickhouse-server/users.d/log_queries.xml
-<clickhouse>
-    <profiles>
-        <default>
-            <log_queries>0</log_queries>
-            <log_query_threads>0</log_query_threads>
-            <log_processors_profiles>0</log_processors_profiles>
-        </default>
-    </profiles>
-</clickhouse>
-```