Fetch observations filtered by trace name in SDK #8026
-
Describe the feature or potential improvement
Additional informationNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
@nikkinxaver Within the UI we have some additional magic to make filtering by trace properties within the observation view more efficient which are not applicable on the SDK. If you query the traces api (https://api.reference.langfuse.com/#tag/trace/get/api/public/traces) each trace will have a list of observation IDs that are attached to it. You could use this list to query the relevant observations in a second step. I believe rebuilding your desired behaviour with the given APIs would be better than modifying the APIs. Let me know in case you have further questions on how to approach this. |
Beta Was this translation helpful? Give feedback.
-
|
The top-down approach does make a lot of sense. Thanks for the quick answer :) |
Beta Was this translation helpful? Give feedback.
-
|
My initial thought was that I could directly see the status of the trace when querying it. So I wondered if the api(https://api.reference.langfuse.com/#tag/trace/get/api/public/traces) could return a trace list with the following data model: { That is, each sub-observation also comes with its corresponding level. I wonder if this can improve the efficiency of querying the trace level? However, it seems that this requirement requires modifying the response data model and the behavior of uploading observation data. btw，thank you for the approach you provided :) |
Beta Was this translation helpful? Give feedback.
@nikkinxaver Within the UI we have some additional magic to make filtering by trace properties within the observation view more efficient which are not applicable on the SDK.
If you query the traces api (https://api.reference.langfuse.com/#tag/trace/get/api/public/traces) each trace will have a list of observation IDs that are attached to it. You could use this list to query the relevant observations in a second step. I believe rebuilding your desired behaviour with the given APIs would be better than modifying the APIs.
Let me know in case you have further questions on how to approach this.