356cc4a0a1
This will allow to easily see how much time is taken up by being able to filter by the `write_bytes_to_request` operation in Jaeger. Spawning from https://github.com/element-hq/synapse/issues/17722 The `write_bytes_to_request` span won't show up in the trace until https://github.com/element-hq/synapse/pull/18849 is merged. Note: It's totally fine for a span child to finish after the parent. See https://opentracing.io/specification/#references-between-spans which shows "Child Span D" outliving the "Parent Span"