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

Manually add OTEL context to both root spans #807

Merged
merged 1 commit into from
Oct 17, 2022

Conversation

saschagrunert
Copy link
Member

@saschagrunert saschagrunert commented Oct 17, 2022

What type of PR is this?

/kind bug

What this PR does / why we need it:

According to open-telemetry/opentelemetry-rust#888 (comment), this works around the issue where the root span is missing from the traces.

Which issue(s) this PR fixes:

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

None

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 17, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

According to
open-telemetry/opentelemetry-rust#888 (comment),
this works around the issue where the root span is missing from the
traces.

Signed-off-by: Sascha Grunert <[email protected]>
@@ -312,7 +312,7 @@ var _ = Describe("ConmonClient", func() {
rssAfter := vmRSSGivenPID(pid)
GinkgoWriter.Printf("VmRSS after: %d\n", rssAfter)
GinkgoWriter.Printf("VmRSS diff: %d\n", rssAfter-rssBefore)
Expect(rssAfter - rssBefore).To(BeNumerically("<", 1200))
Expect(rssAfter - rssBefore).To(BeNumerically("<", 1500))
Copy link
Member Author

Choose a reason for hiding this comment

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

The integration tests seemed to flake more lately. Not really related to this PR, but should make them more resilient.

@haircommander
Copy link
Collaborator

/lgtm

@saschagrunert
Copy link
Member Author

Tide seems to not react on the state of this PR 🤔

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