From cc0c84570cd0d0d7c7383760a98d60a33987498a Mon Sep 17 00:00:00 2001 From: squahtx Date: Fri, 4 Nov 2022 15:23:09 +0000 Subject: deploy: e5d18956b9e58ec15f1c89b8b625065611ed413d --- develop/upgrade.html | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'develop/upgrade.html') diff --git a/develop/upgrade.html b/develop/upgrade.html index 2fd643a761..c1fbadfd57 100644 --- a/develop/upgrade.html +++ b/develop/upgrade.html @@ -249,6 +249,16 @@ room to be interesting to the application service.

this will no longer match as you expect. The behavioral mismatch between matching all local users and some remote users is why the spec was changed/clarified and this caveat is no longer supported.

+

Legacy Prometheus metric names are now disabled by default

+

Synapse v1.71.0 disables legacy Prometheus metric names by default. +For administrators that still rely on them and have not yet had chance to update their +uses of the metrics, it's still possible to specify enable_legacy_metrics: true in +the configuration to re-enable them temporarily.

+

Synapse v1.73.0 will remove legacy metric names altogether and at that point, +it will no longer be possible to re-enable them.

+

If you do not use metrics or you have already updated your Grafana dashboard(s), +Prometheus console(s) and alerting rule(s), there is no action needed.

+

See v1.69.0: Deprecation of legacy Prometheus metric names.

Upgrading to v1.69.0

Changes to the receipts replication streams

Synapse now includes information indicating if a receipt applies to a thread when -- cgit 1.5.1