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
Add Attributes connection.transport_failure_reason #26710
Comments
cc @kyessenov |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
@mattklein123 could you add a "help wanted" tag to revive this issue? |
…attribute (#31058) Co-authored-by: Xinyi Zhang <zhaxny@amazon.com> Reviving: #29180 Commit Message: attributes: expose DOWNSTREAM_TRANSPORT_FAILURE_REASON as connection attribute Additional Description: Earlier PR #25322 added `DOWNSTREAM_TRANSPORT_FAILURE_REASON` to access log. This PR exposes it to be one of the attributes that other extension can have access to such as WASM filter. This attribute would play as a similar role to `upstream.transport_failure_reason` from upstream attributes. Risk Level: Low Testing: Unit testing Docs Changes: Yes Release Notes: Yes Platform Specific Features: Fixes: #26710
Title: Add Attributes connection.transport_failure_reason along with TLS connection errors
Description:
[optional Relevant Links:]
The text was updated successfully, but these errors were encountered: