Replies: 6 comments
-
Hey @RAPHCVR! 👋 I'm here to help you with any bugs, questions, or contributions. Let's get to the bottom of this! If traces are visible through the API but not in the web UI, there could be several reasons for this discrepancy:
Review these areas to identify and resolve the issue with trace visibility in the web UI. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Beta Was this translation helpful? Give feedback.
-
It seems it has to do with clickhouse pod, does someone have a hint ? |
Beta Was this translation helpful? Give feedback.
-
Did you just update to v3? Do you see that any background migrations are still running? |
Beta Was this translation helpful? Give feedback.
-
Thanks for your reply @marcklingen, I tried to release langfuse again from scratch, and the issue is not there from now it seems (as with my first deployment), but maybe the traces will disappear again, I have this error in clickhouse that was also present when the bug was occuring:
I have this error with the clickhouse pods. |
Beta Was this translation helpful? Give feedback.
-
Hey @marcklingen, I still have this error in my Clickhouse pod (I am using Kubernetes for deployment). |
Beta Was this translation helpful? Give feedback.
-
Hey, on my self hosted langfuse, traces are available through the api it seems:
Indeed there is plenty of elements here.
But, on the webui, only 3 traces are available (all trace were there this morning, I haven't touched anything), I tried to update to the latest version, but it did not solve the issue.
Finally, I am using Kubernetes with the provided helm chart from the docs.
Thanks in advance for your help !
Beta Was this translation helpful? Give feedback.
All reactions