Replies: 2 comments 1 reply
-
We have not exposed span start/end time as intrinsics but I don't think it would be terribly difficult. I believe we'd need a new data type in the query language (datetime) but other than that I could link to several PRs that accomplish this for different fields. Do you mind creating an issue? I can mark it as a requested feature and we can prioritize it. It may take a bit for us to get to it internally, but at least it would be on the list and folks in the community could attempt it. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Converted into an issue here: #4966. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Howdy,
I'm trying to investigate a pod-scoped event that I know occurred at around time T. (In my case it's an asyncio event loop stall but it could have been a deadlock, an OOM event or something similar.)
I'd love it if I could put together a TraceQL query to return traces with spans that start before time T, and end afterwards (alongside filtering by the pod name, but that's already possible). From what I can gather, such a query is not currently possible.
Beta Was this translation helpful? Give feedback.
All reactions