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

try to fix tracing #9625

Closed
wants to merge 1 commit into from
Closed

try to fix tracing #9625

wants to merge 1 commit into from

Conversation

AlexTugarev
Copy link
Member

follow-up to #9281

  • /werft with-observability=true
  • /werft with-helm=true
  • /werft with-clean-slate-deployment
NONE

@AlexTugarev
Copy link
Member Author

AlexTugarev commented Apr 28, 2022

/werft run

👍 started the job as gitpod-build-at-mess-with-tracing.1
(with .werft/ from main)

@@ -28,7 +28,8 @@ export namespace TraceContext {
if (!!parentCtx?.span) {
const ctx = parentCtx?.span?.context();
if (ctx && !!ctx.toTraceId() && !!ctx.toSpanId()) {
options.references = [opentracing.followsFrom(ctx)];
// options.references = [opentracing.followsFrom(ctx)];
options.childOf = ctx;
Copy link
Member Author

Choose a reason for hiding this comment

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

@geropl, wdyt, should we remove these entirely?
frankly, I don't understand the issue at hand, but given I started #9281, I'd like to find an end to this story.
what option do we have? if we revert, we end up with messed up logs.

Copy link
Member Author

Choose a reason for hiding this comment

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

@geropl, is this still an issue?

Copy link
Member

Choose a reason for hiding this comment

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

No, I think we should leave it as-is. The problems we faced were mostly solved by Mad's attempts to find dangling spans that were not finish()ed. 👍

@stale
Copy link

stale bot commented Jun 10, 2022

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added meta: stale This issue/PR is stale and will be closed soon and removed meta: stale This issue/PR is stale and will be closed soon labels Jun 10, 2022
@AlexTugarev
Copy link
Member Author

Closing, because I'm out of ideas on this.

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.

3 participants