Replies: 1 comment
-
|
Hi @XyAgent, thanks for adding this. |
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Facilitate Evaluation / BDD and TDD flow
Currently, langfuse provides a very convenient set up to catch application traces, including Agentic (Langgraph-like) traces with detailed steps description, intermediate data transformations, etc.
All those traces and up being stored inside Clickhouse (either launched locally or on a dedicated machine/cloud)
Which is suitable for monitoring, but, sadly, not very convenient for debugging and evaluation purposes
We end up using deepeval, which provides an ability to launch experiments and save evaluation results locally (in a .json file), but I should tell that we are very unhappy to maintain a heavy additional dependency + set up a duplicate observation logic
If only langfuse would provide a way to store traces locally (inside an .sqlite base, for example, or just a plain .json)
this would allow to:
Making Langfuse an all-in-one solution for testing, evaluation, monitoring, which is currently a pain point
P.S. I thought about langfuse self-hosted runs to address this problem, but:
P.S.S.
The thing is not about sqlite or any other particular instrument to store the traces locally, it's more about an abstract class
which would provide an ability to attach a custom trace exporter (which would flush the traces whenever the user wants to)
Just like attaching a custom
httpx clientwhen initializingLangfuseobject, but for tracesAdditional information
No response
Beta Was this translation helpful? Give feedback.
All reactions