This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Be able to correlate traces even when Cloudflare times out #13685
Labels
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-Enhancement
New features, changes in functionality, improvements in performance, or user-facing enhancements.
When Synapse responds successfully, we add a
synapse-trace-id
header which makes it nice and easy to jump to the trace in Jaeger.But when a Cloudflare timeout gets in the way, we just see a
524: A timeout occurred
. The Cloudflare response does have a Cloudflare specificcf-ray
header which we could include in the tags of top-level servlet tracing span. This is even what Cloudflare essentially suggests:This is a bit specific to
matrix.org
which uses Cloudflare so perhaps we want to add some Synapse config to specify which request header field to pull from and add as a tag to the servlet tracing span.The text was updated successfully, but these errors were encountered: