tracing: Investigate supporting header sanitization for x-envoy-decorator-operation #1889
Assignees
Labels
Comments
jpsim
pushed a commit
that referenced
this issue
Nov 28, 2022
…es (#1889) Description: When switching from the default socket mode to alternate bound interface mode, this change adds extra information to the LOG_EVENT, capturing the first active interface for IPv4 and IPv6 meeting the selection criteria for the alternate network. Risk Level: Low Testing: CI Signed-off-by: Mike Schore <mike.schore@gmail.com> Signed-off-by: JP Simard <jp@jpsim.com>
jpsim
pushed a commit
that referenced
this issue
Nov 29, 2022
…es (#1889) Description: When switching from the default socket mode to alternate bound interface mode, this change adds extra information to the LOG_EVENT, capturing the first active interface for IPv4 and IPv6 meeting the selection criteria for the alternate network. Risk Level: Low Testing: CI Signed-off-by: Mike Schore <mike.schore@gmail.com> Signed-off-by: JP Simard <jp@jpsim.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tried adding this in #1858 but it prevented the header being propagated from the egress to ingress listeners between services in the jaegertracing (and therefore probably zipkin) example.
The text was updated successfully, but these errors were encountered: