From 088d0fbd69b7b699a2242797989da10d11d42860 Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Wed, 25 May 2022 09:14:38 +0000 Subject: [PATCH] deploy: 298911555c2572da823398f2816846f7353e89e9 --- develop/message_retention_policies.html | 2 +- develop/print.html | 6 +++--- develop/searchindex.js | 2 +- develop/searchindex.json | 2 +- develop/structured_logging.html | 2 +- develop/workers.html | 2 +- 6 files changed, 8 insertions(+), 8 deletions(-) diff --git a/develop/message_retention_policies.html b/develop/message_retention_policies.html index dd3d035c07..df04acaba4 100644 --- a/develop/message_retention_policies.html +++ b/develop/message_retention_policies.html @@ -239,7 +239,7 @@ policy's max_lifetime is greater than a week.

Note that this example is tailored to show different configurations and features slightly more jobs than it's probably necessary (in practice, a server admin would probably consider it better to replace the two last -jobs with one that runs once a day and handles rooms which which +jobs with one that runs once a day and handles rooms which policy's max_lifetime is greater than 3 days).

Keep in mind, when configuring these jobs, that a purge job can become quite heavy on the server if it targets many rooms, therefore prefer diff --git a/develop/print.html b/develop/print.html index 6865813ae1..fe002be8a4 100644 --- a/develop/print.html +++ b/develop/print.html @@ -9118,7 +9118,7 @@ loggers:

The above logging config will set Synapse as 'INFO' logging level by default, with the SQL layer at 'WARNING', and will log to a file, stored as JSON.

-

It is also possible to figure Synapse to log to a remote endpoint by using the +

It is also possible to configure Synapse to log to a remote endpoint by using the synapse.logging.RemoteHandler class included with Synapse. It takes the following arguments: