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 to release/3.4.x] fix(tracing): set parent span correctly (#11786) #11831

Merged
merged 1 commit into from
Oct 25, 2023

Conversation

samugi
Copy link
Member

@samugi samugi commented Oct 24, 2023

Backport of #11786

Note: the bug was introduced by #11468 where the parent_id was incorrectly updated on the balancer span instead of the root span. This PR reverts that part.

Summary

When the balancer instrumentation was enabled, the parent span was set incorrectly on traces, this fix addresses the problem by setting the parent span correctly on the root (kong) span when there is an incoming tracing header.

Checklist

  • The Pull Request has tests
  • A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
  • (no) There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

  • [Implement ...]

Issue reference

KAG-2811
FTI-5485

when the `balancer` instrumentation was enabled, the parent span
was set incorrectly on traces, this fix addresses the problem by
setting the parent span correctly on the root (`kong`) span when
there is an incoming tracing header.
Copy link
Contributor

@nowNick nowNick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@samugi samugi merged commit e49fbd6 into release/3.4.x Oct 25, 2023
28 checks passed
@samugi samugi deleted the backport-11786-to-release/3.4.x branch October 25, 2023 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants