Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

propagate spans to tasks spawned by Hyper #550

Merged
merged 1 commit into from
Jun 8, 2020

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 eliza@buoyant.io

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 <eliza@buoyant.io>
@hawkw hawkw requested review from olix0r and a team 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