Skip to content
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

Backport of docs(lambda-extension): update distributed tracing headers warning; into release/1.17.x #28460

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions website/content/docs/platform/aws/lambda-extension.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -243,12 +243,16 @@ request will be forwarded to Vault and the response returned and cached.
Currently, the cache key is a hash of the request URL path, headers, body, and
token.

<Warning title="Distributed tracing headers may negate the cache">

The Vault Lambda Extension cache key includes headers from proxy requests. As
a result, distributed tracing headers like `traceparent` can lead to
individualized hashes that make repeated requests appear unique and cause cache
misses.
<Warning title="Nonstandard distributed tracing headers may negate the cache">

The Vault Lambda Extension cache key includes headers from proxy requests, but
excludes the standard distributed tracing headers `traceparent` and
`tracestate` because trace IDs are unique per request and would lead to unique
hashes for repeated requests.

Some distributed tracing tools may add nonstandard tracing headers, which can
also lead to individualized hashes that make repeated requests unique and
cause cache misses.

</Warning>

Expand Down
Loading