kaslo/synapse
1
0
Fork 0
Code Wiki Activity

deploy: f13a136396

Browse Source
This commit is contained in:
MadLittleMods
2025-07-29 15:40:38 +00:00
parent b4987a4abc
commit c39a79f226
4 changed files with 30 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
develop/print.html
View File

@@ -1890,6 +1890,20 @@ database migrations are complete. You should wait until background updates from
each upgrade are complete before moving on to the next upgrade, to avoid
stacking them up. You can monitor the currently running background updates with
<a href="usage/administration/admin_api/background_updates.html#status">the Admin API</a>.</p>
<h1 id="upgrading-to-v11360"><a class="header" href="#upgrading-to-v11360">Upgrading to v1.136.0</a></h1>
<h2 id="metric-labels-have-changed-on-synapse_federation_last_received_pdu_time-and-synapse_federation_last_sent_pdu_time"><a class="header" href="#metric-labels-have-changed-on-synapse_federation_last_received_pdu_time-and-synapse_federation_last_sent_pdu_time">Metric labels have changed on <code>synapse_federation_last_received_pdu_time</code> and <code>synapse_federation_last_sent_pdu_time</code></a></h2>
<p>Previously, the <code>synapse_federation_last_received_pdu_time</code> and
<code>synapse_federation_last_sent_pdu_time</code> metrics both used the <code>server_name</code> label to
differentiate between different servers that we send and receive events from.</p>
<p>Since we're now using the <code>server_name</code> label to differentiate between different Synapse
homeserver instances running in the same process, these metrics have been changed as follows:</p>
<ul>
<li><code>synapse_federation_last_received_pdu_time</code> now uses the <code>origin_server_name</code> label</li>
<li><code>synapse_federation_last_sent_pdu_time</code> now uses the <code>destination_server_name</code> label</li>
</ul>
<p>The Grafana dashboard JSON in <code>contrib/grafana/synapse.json</code> has been updated to reflect
this change but you will need to manually update your own existing Grafana dashboards
using these metrics.</p>
<h1 id="upgrading-to-v11350"><a class="header" href="#upgrading-to-v11350">Upgrading to v1.135.0</a></h1>
<h2 id="on_user_registration-module-api-callback-may-now-run-on-any-worker"><a class="header" href="#on_user_registration-module-api-callback-may-now-run-on-any-worker"><code>on_user_registration</code> module API callback may now run on any worker</a></h2>
<p>Previously, the <code>on_user_registration</code> callback would only run on the main

2
develop/searchindex.js
View File

File diff suppressed because one or more lines are too long

2
develop/searchindex.json
View File

File diff suppressed because one or more lines are too long

14
develop/upgrade.html
View File

@@ -285,6 +285,20 @@ database migrations are complete. You should wait until background updates from
each upgrade are complete before moving on to the next upgrade, to avoid
stacking them up. You can monitor the currently running background updates with
<a href="usage/administration/admin_api/background_updates.html#status">the Admin API</a>.</p>
<h1 id="upgrading-to-v11360"><a class="header" href="#upgrading-to-v11360">Upgrading to v1.136.0</a></h1>
<h2 id="metric-labels-have-changed-on-synapse_federation_last_received_pdu_time-and-synapse_federation_last_sent_pdu_time"><a class="header" href="#metric-labels-have-changed-on-synapse_federation_last_received_pdu_time-and-synapse_federation_last_sent_pdu_time">Metric labels have changed on <code>synapse_federation_last_received_pdu_time</code> and <code>synapse_federation_last_sent_pdu_time</code></a></h2>
<p>Previously, the <code>synapse_federation_last_received_pdu_time</code> and
<code>synapse_federation_last_sent_pdu_time</code> metrics both used the <code>server_name</code> label to
differentiate between different servers that we send and receive events from.</p>
<p>Since we're now using the <code>server_name</code> label to differentiate between different Synapse
homeserver instances running in the same process, these metrics have been changed as follows:</p>
<ul>
<li><code>synapse_federation_last_received_pdu_time</code> now uses the <code>origin_server_name</code> label</li>
<li><code>synapse_federation_last_sent_pdu_time</code> now uses the <code>destination_server_name</code> label</li>
</ul>
<p>The Grafana dashboard JSON in <code>contrib/grafana/synapse.json</code> has been updated to reflect
this change but you will need to manually update your own existing Grafana dashboards
using these metrics.</p>
<h1 id="upgrading-to-v11350"><a class="header" href="#upgrading-to-v11350">Upgrading to v1.135.0</a></h1>
<h2 id="on_user_registration-module-api-callback-may-now-run-on-any-worker"><a class="header" href="#on_user_registration-module-api-callback-may-now-run-on-any-worker"><code>on_user_registration</code> module API callback may now run on any worker</a></h2>
<p>Previously, the <code>on_user_registration</code> callback would only run on the main