Skip to content

propagate spans to tasks spawned by Hyper#550

Merged
hawkw merged 1 commit intomaster-tokio-0.2from
eliza/0.2-span-exec
Jun 8, 2020
Merged

propagate spans to tasks spawned by Hyper#550
hawkw merged 1 commit intomaster-tokio-0.2from
eliza/0.2-span-exec

Conversation

@hawkw
Copy link
Contributor

@hawkw hawkw commented Jun 4, 2020

Previously, in the futures 0.1 version of the proxy, we provided
hyper with a custom executor to propagate tracing spans to tasks
spawned by hyper. In the process of updating the proxy to
std::future, this was removed, meaning that any tasks spawned by hyper
are missing their spans. This makes events recorded by h2 and so on
hard to debug, especially when many connections are open.

This branch fixes this by adding an implementation of hyper::Executor
that propagates the current span when spawning a task.

Signed-off-by: Eliza Weisman [email protected]

Previously, in the `futures` 0.1 version of the proxy, we provided
`hyper` with a custom executor to propagate `tracing` spans to tasks
spawned by `hyper`. In the process of updating the proxy to
`std::future`, this was removed, meaning that any tasks spawned by hyper
are missing their spans. This makes events recorded by `h2` and so on
hard to debug, especially when many connections are open.

This branch fixes this by adding an implementation of `hyper::Executor`
that propagates the current span when spawning a task.

Signed-off-by: Eliza Weisman <[email protected]>
@hawkw hawkw requested review from a team and olix0r June 4, 2020 21:46
Copy link
Contributor

@kleimkuhler kleimkuhler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@hawkw hawkw merged commit 6105918 into master-tokio-0.2 Jun 8, 2020
@olix0r olix0r deleted the eliza/0.2-span-exec branch May 25, 2021 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants