fix(stackable-telemetry/webhook): Correctly extract connect and host info in Axum trace layer #806
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NickLarsenNZ
previously approved these changes
Jun 12, 2024
Techassi
deleted the
fix/stackable-telemetry-connect-info-and-host-header
branch
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This correctly extract the
server.address,server.port,client.addressandclient.portfields in the OpenTelemetry compatible traces.This fix requires changes in the
stackable-webhookcrate to instruct various parts of the connection handling chain to extract the required data, which can be consumed by thestackable-telemetrycrate.Screenshot