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

export unclosed span #2752

Closed
LilyHolms opened this issue Jun 9, 2022 · 9 comments
Closed

export unclosed span #2752

LilyHolms opened this issue Jun 9, 2022 · 9 comments
Labels
feature-request question Further information is requested

Comments

@LilyHolms
Copy link

We are using BatchSpanProcessor to batch spans and pushes them to jaeger exporter.
We noticed a span is exported only when it ends.

However, our system have root span which runs across different microservice, and we hope to query span attributes from db before the span finishes.

Is there a way for us to export span once it starts, and update the span on any change in attributes or span status?

@srikanthccv
Copy link
Member

That's not possible

@LilyHolms
Copy link
Author

Well, is it possible to attach extra attributes after a span ends?

@srikanthccv
Copy link
Member

is it possible to attach extra attributes after a span ends

No, they are discarded after it ends.

@aabmass
Copy link
Member

aabmass commented Jun 10, 2022

Is there a way for us to export span once it starts, and update the span on any change in attributes or span status?

I'm curious if Jaeger even supports this

However, our system have root span which runs across different microservice, and we hope to query span attributes from db before the span finishes.

If you don't mind expanding a bit, what does the downstream service do with those attributes? I wouldn't count on the root span being queryable from Jaeger before the second downstream microservice queries it.

Have you looked into Baggage? This is good way to propagate some attributes downstream.

@bigqi0812
Copy link

@aabmass @srikanthccv I have the same question. What's the recommended way to keep track of the on-going spans if a span is going to take long time to end?

@srikanthccv
Copy link
Member

@bigqi0812 What's your use case? How long does it take to complete?

The best option I can think of is zpages but we don't have that as of today https://github.com/open-telemetry/opentelemetry-specification/blob/main/experimental/trace/zpages.md#overview

@srikanthccv srikanthccv added the question Further information is requested label Jun 22, 2022
@simingy
Copy link

simingy commented Jul 11, 2022

What Lily is asking is similar to open-telemetry/opentelemetry-specification#373

without that - we is there a way for us to view "current/inflight/inprogress" spans? @srikanthccv

@srikanthccv
Copy link
Member

No, currently there is no way to do that other than what I previously mentioned.

@srikanthccv
Copy link
Member

One can probably build a custom span processor + exporter combination to achieve but not something supported. Please raise a feature request in https://github.com/open-telemetry/opentelemetry-specification.

@srikanthccv srikanthccv closed this as not planned Won't fix, can't repro, duplicate, stale Feb 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants