Issue with Missing Sessions During Span Transfer on UI
Hey Team, While doing span transfer from one project to another it missed sessions on UI. is it bug or it is how it is?
Hey Team, While doing span transfer from one project to another it missed sessions on UI. is it bug or it is how it is?
Hey Darshan T. this is correct, the transfer feature only transfers the trace as a session can span multiple traces. The original design of this feature was intended for retention of annotations. I think to make this sufficiently work consistently we'd have to build transfer session as sessions are runtime recordings and there is messiness in transferring it. Can you help me better understand why you are trying to transfer the session over to another project?
one basic reason: to keep everything at one place, I can easily search for any record based on session id in same project in case i delete older project will i lose my sessions details?
I guess more concretely what is the project you are transferring the data to called - is it interesting sessions or cold storage?
Yes so basically from all the list of sessions I've in one project, few interactions which i want annotate and want to keep it separate rather than searching in one big project. Keeping it separate make things easier for me. and one more observation. when we create dataset from selected spans. If i add annotation on actual span, it is not reflected on dataset
Gotcha, on point 1 I think this makes a lot of sense but we'd have to probably build "transfer session" as there's some nuanced issues around when sessions end that it doesn't make sense to transfer the session when 1 trace is transferred. On 2, that seems like a bug depending on your flow. When you transfer 1 span you don't see the annotations in the dataset metadata?
While creating dataset at first, it has annotation in metadata, but after that if I add further more annotation on same span it is not reflected on metadata
I see, yeah the dataset only captures the annotations when the dataset is created. They are not linked forever since the dataset content is versioned independently from the span. I get your pain here, but also a bit of a design decision since we typically would transfer interesting examples to a dataset post annotation. I guess what's the workflow behind annotating the spans after it's been added to a dataset?
So before moving spans to different project, I thought of keeping them into dataset but that's not good idea i feel....
I think the typical workflow we imagine is that annotations happen on traces as part of an annotation workflow. Then you want to pick and choose which ones you want to transfer to a dataset (e.g. pick the interesting ones to move to a regression suite). Otherwise I think there's no real reason to move them to a dataset as the traces probably contain a lot more rich information
But happy to explore both areas for sure. Annotations on datasets themselves make some level of sense too, which is why we have things like splits.
Def. file us github issues and we can try to iron out some of the pains you're feeling
Sure, Thanks for help :)
No worries, thanks for the feedback. Keep it coming