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

fix(undici): avoid possible duplicate 'traceparent' header on instrumented HTTP requests #3965

Merged
merged 1 commit into from
Apr 11, 2024

Conversation

trentm
Copy link
Member

@trentm trentm commented Apr 10, 2024

... because Elasticsearch borks on these requests. This case should only be
possible in a weird case like having two APM agents active.

Fixes: #3964


We might want to add a similar guard to OTel's undici instr as well.

…ented HTTP requests

... because Elasticsearch borks on these requests. This case should only be
possible in a weird case like having two APM agents active.

Fixes: #3964
@trentm trentm requested a review from david-luna April 10, 2024 22:55
@trentm trentm self-assigned this Apr 10, 2024
@trentm trentm merged commit 526486f into main Apr 11, 2024
19 checks passed
@trentm trentm deleted the trentm/undici5-dupe-headers branch April 11, 2024 15:26
fpm-peter pushed a commit to fpm-git/apm-agent-nodejs that referenced this pull request Aug 20, 2024
…ented HTTP requests (elastic#3965)

... because Elasticsearch borks on these requests. This case should only be
possible in a weird case like having two APM agents active.

Fixes: elastic#3964
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.

undici instrumentation can add duplicate trace-context headers, which can break Elasticsearch
2 participants