I have had langfuse deployed and self-
I have had langfuse deployed and self-hosted for about 2 months now, and it has worked smoothly. Today, I started seeing a strange timeout error -- I wouldn't expect it to be through our deployment infra, but I wanted to drop here to see if you had any recommendations (see thread)
4 Replies
Any ideas as to why this request timeout would occur? This error occurs from the requesting application -- The traces actually do make it through to the database and show appropriately in the frontend
So I only saw this in the langserve output logs and not in langfuse logs
hmm... actually I am getting some odd traces now as well. Some extraneous and erroneous traces that are nonsensical
Interesting. Are you on the latest version of the Langfuse Python sdk?
We are on 2.16.2 for the python sdk... I think I figured out the issue actually -- seems like we were submitting too many requests to the langfuse deployment, so I created replica service deployments which seems to have handled it
I will let you know if the issue arises again
I’d recommend to automatically scale the container instance if possible
If you write heavily in a short period of time, IOPS of the database could be the bottleneck but you’d see related errors in the container instance logs