-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Meta: Tracing #2678
Comments
@seanmonstar do you want to ignore events that are not in the context of a span? Currently, it appears these events come from within Hyper, as well as external crates, e.g. Using:
the span-free events currently look like:
|
Recording some issues related to OpenTelemetry, these do not appear to impact other layers (json, print, jounald).
|
Adding some context on seanmonstar/warp#923: from a server point of view, it would be useful to have a span that is valid from the first byte received to the last byte sent. Otherwise, when using the Such a span would need to be changed for each new request on an existing connection (in keep alive) for integration with opentelemetry. I have looked a bit at how it could be implemented, at least for HTTP1, that would require adding a span member to |
@Geal this is exactly how tower-http's |
@davidpdrsn Thanks, that worked perfectly |
Related #56 |
hyper uses tracing for logging and events. This issue is meant to be a meta or tracking issue around the overall usage of
tracing
inside hyper. Eventually, users should be able to depend on certain spans and events. Which exactly, we need to figure out.Relevant issues
tracing
support "unstable" if not also 1.0The text was updated successfully, but these errors were encountered: