X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/cf1dcfb8715822f7ac5fe4fce067197dd84bad54..e838828374ceed5ef6da260939251e86f72b6f27:/doc/admin/logs-table-management.html.textile.liquid

diff --git a/doc/admin/logs-table-management.html.textile.liquid b/doc/admin/logs-table-management.html.textile.liquid
index dedd960f88..a1cdb18dcf 100644
--- a/doc/admin/logs-table-management.html.textile.liquid
+++ b/doc/admin/logs-table-management.html.textile.liquid
@@ -25,11 +25,24 @@ h3. API Server configuration
 
 To solve the problem mentioned above, the API server offers the possibility to limit the amount of log information stored on the table:
 
+<pre>
+# Attributes to suppress in events and audit logs.  Notably,
+# specifying ["manifest_text"] here typically makes the database
+# smaller and faster.
+#
+# Warning: Using any non-empty value here can have undesirable side
+# effects for any client or component that relies on event logs.
+# Use at your own risk.
+unlogged_attributes: []
+</pre>
+
+The above setting affects all events being logged, independently of how much time they will be kept on the database.
+
 <pre>
 # Time to keep audit logs (a row in the log table added each time an
 # Arvados object is created, modified, or deleted) in the PostgreSQL
 # database. Currently, websocket event notifications rely on audit
-# logs, so this should not be set lower than 600 (10 minutes).
+# logs, so this should not be set lower than 300 (5 minutes).
 max_audit_log_age: 1209600
 </pre>