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>
# Arvados object is created, modified, or deleted.)
#
# Currently, websocket event notifications rely on audit logs, so
- # this should not be set lower than 600 (5 minutes).
+ # this should not be set lower than 300 (5 minutes).
MaxAge: 1209600
# Maximum number of log rows to delete in a single SQL transaction.