This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
LoggingContext.tag
being lost on metrics and traces
#15920
Labels
A-Logging
Synapse's logs (structured or otherwise). Not metrics.
A-Metrics
metrics, measures, stuff we put in Prometheus
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Minor
Blocks non-critical functionality, workarounds exist.
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Z-Dev-Wishlist
Makes developers' lives better, but doesn't have direct user impact
As discovered during the discussion in #15708 (comment),
Background
LoggingContext.tag
was introduced to differentiate what kind of sync was happening in our metrics. The only place we populate it is for this use case even though it could be used generally:synapse/synapse/handlers/sync.py
Lines 348 to 357 in a424318
We also use it in the tracing with
SynapseTags.REQUEST_TAG
which says that it's "used to distinguish full vs incremental syncs, etc".Problem
If I look at the Prometheus data, I don't see any data for
matrix.org
. I only see it for one other instance we track which is running Synapse 1.83.0. Has it broken since then?And if I look at the traces,
request_tag
is always set to the default empty string when I look at thoseSyncRestServlet
traces (also checkedRoomInitialSyncRestServlet
).It seems like the context is being lost somewhere.
The text was updated successfully, but these errors were encountered: