Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a request-id example using tower, tower-http, and tracing.
Motivation
This is something I've had to do a few times now in axum that I had to figure out through a combination of axum docs and tower-http docs. Having a concrete example shows a way of doing this in a way that axum supports without having to dig through 2 docs.rs pages (or 3 if you're looking in tower as well).
Figuring out the middleware, the order, and how to write the
TraceLayer
to avoid extra clones has prevented issues for other engineers I've interacted with as well, so the goal is also to clarify an easy way to achieve request ids.Solution
examples/request-id
.tower
andtower-http
crates to handle request-id middleware.tracing
andtracing-subscriber
crates to show how to add these request ids to each requests span.