From ca3c07e833816e69bbaf0372e6cc79f52e6db88e Mon Sep 17 00:00:00 2001 From: Eric Eastwood Date: Fri, 19 May 2023 11:18:45 -0500 Subject: [PATCH] Trace how many new events from the backfill response we need to process (#15633) You can kinda derive this information from how many `_process_pulled_event` spans there are but it would be nice to quickly glance. --- changelog.d/15633.misc | 1 + synapse/handlers/federation_event.py | 5 +++++ 2 files changed, 6 insertions(+) create mode 100644 changelog.d/15633.misc diff --git a/changelog.d/15633.misc b/changelog.d/15633.misc new file mode 100644 index 000000000..4126a2060 --- /dev/null +++ b/changelog.d/15633.misc @@ -0,0 +1 @@ +Trace how many new events from the backfill response we need to process. diff --git a/synapse/handlers/federation_event.py b/synapse/handlers/federation_event.py index 06343d40e..9a08618da 100644 --- a/synapse/handlers/federation_event.py +++ b/synapse/handlers/federation_event.py @@ -890,6 +890,11 @@ class FederationEventHandler: # Continue on with the events that are new to us. new_events.append(event) + set_tag( + SynapseTags.RESULT_PREFIX + "new_events.length", + str(len(new_events)), + ) + # We want to sort these by depth so we process them and # tell clients about them in order. sorted_events = sorted(new_events, key=lambda x: x.depth)