8000 Fix route labels on outbound tap metadata by olix0r · Pull Request #1247 · linkerd/linkerd2-proxy · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fix route labels on outbound tap metadata #1247

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

Merged
merged 1 commit into from
Sep 8, 2021
Merged

Fix route labels on outbound tap metadata #1247

merged 1 commit into from
Sep 8, 2021

Conversation

olix0r
Copy link
Member
@olix0r olix0r commented Sep 8, 2021

The outbound proxy did not properly expose route labels to tap on
outbound requests. This change ensures that route labels are set on
outbound requests for display by tap.

The outbound proxy did not properly expose route labels to tap on
outbound requests. This change ensures that route labels are set on
outbound requests for display by tap.
@olix0r olix0r requested a review from a team September 8, 2021 02:56
@olix0r olix0r merged commit 47a5757 into main Sep 8, 2021
@olix0r olix0r deleted the ver/route-ext branch September 8, 2021 15:51
olix0r added a commit to linkerd/linkerd2 that referenced this pull request Sep 9, 2021
This release improves error handling so that HTTP metrics include 5XX
responses for common errors.

Logging has also been improved to ensure `inbound` and `outbound` spans
are always present in log messages.

Outbound tap has been fixed to include route labels when service
profiles are configured.

---

* Set tracing spans on policy client (linkerd/linkerd2-proxy#1241)
* build(deps): bump tokio-util from 0.6.7 to 0.6.8 (linkerd/linkerd2-proxy#1240)
* core: fix missing spans in `serve` tasks (linkerd/linkerd2-proxy#1243)
* build(deps): bump thiserror from 1.0.28 to 1.0.29 (linkerd/linkerd2-proxy#1244)
* orig-proto: Avoid emiting HTTP/2 errors for upgraded requests (linkerd/linkerd2-proxy#1245)
* Fix route labels on outbound tap metadata (linkerd/linkerd2-proxy#1247)
* errors: Support contextual error handling strategies (linkerd/linkerd2-proxy#1246)
olix0r added a commit to linkerd/linkerd2 that referenced this pull request Sep 9, 2021
This release improves error handling so that HTTP metrics include 5XX
responses for common errors.

Logging has also been improved to ensure `inbound` and `outbound` spans
are always present in log messages.

Outbound tap has been fixed to include route labels when service
profiles are configured.

---

* Set tracing spans on policy client (linkerd/linkerd2-proxy#1241)
* build(deps): bump tokio-util from 0.6.7 to 0.6.8 (linkerd/linkerd2-proxy#1240)
* core: fix missing spans in `serve` tasks (linkerd/linkerd2-proxy#1243)
* build(deps): bump thiserror from 1.0.28 to 1.0.29 (linkerd/linkerd2-proxy#1244)
* orig-proto: Avoid emiting HTTP/2 errors for upgraded requests (linkerd/linkerd2-proxy#1245)
* Fix route labels on outbound tap metadata (linkerd/linkerd2-proxy#1247)
* errors: Support contextual error handling strategies (linkerd/linkerd2-proxy#1246)
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.

2 participants
0