switch from jaeger-client to opentelemetry #11850

Activity

1. clokep

   added

   T-TaskRefactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.

   A-PerformancePerformance, both client-facing and admin-facingPerformance, both client-facing and admin-facing

   on Feb 1, 2022
2. MadLittleMods

   added a commit that references this issue on Jul 26, 2022

   Migrate to OpenTelemetry tracing

   ...

   0cc610e
3. MadLittleMods commented on Aug 4, 2022

   

   MadLittleMods

   on Aug 4, 2022

   Contributor

   More actions

   This will require rewriting, or replacing, https://github.com/erikjohnston/rust-jaeger-python-client

   Got some more context from @erikjohnston on why we need the Rust exporter and it boils down to using a Python reporter/exporter can easily slow down the rest of Synapse. Python is slower than Rust but also the Python global interpreter lock (GIL) prevents multi-threaded work from being faster (🙇 hopefully not too off)

   ---

   There is some uncertainty of moving to OpenTelemetry because of drama and unclear from the outside what the current state is of anything. [TODO: any details?]
4. MadLittleMods commented on Oct 20, 2022

   

   MadLittleMods

   on Oct 20, 2022

   Contributor

   More actions

   There is some uncertainty of moving to OpenTelemetry because of drama and unclear from the outside what the current state is of anything. [TODO: any details?]

   This point is no longer relevant. This was touched on in the August backend chapter meeting and turned out to really be of no substance. Perhaps just murmurings when the project was first getting going. But seems like the canonical new choice to go to now.
5. yu-re-ka commented on Oct 23, 2023

   

   yu-re-ka

   on Oct 23, 2023

   More actions

   opentracing breaks with asyncio changes in Python 3.11, so now would be a good time to migrate