Disabling media uploads in self-hosted environment

[mrPsycox]

Describe the bug

I set up my self hosted installation by configuring these environment variables to use minio and manage my multimodal traces:

LANGFUSE_MAX_EVENT_SIZE_BYTES
LANGFUSE_MAX_BATCH_SIZE_BYTES
LANGFUSE_S3_EVENT_UPLOAD_BUCKET
LANGFUSE_S3_EVENT_UPLOAD_ENDPOINT
LANGFUSE_S3_EVENT_UPLOAD_FORCE_PATH_STYLE
LANGFUSE_S3_MEDIA_UPLOAD_BUCKET

when the trace in response is processed (which contexts with base64 strings) it seems that langfuse looks for some media upload, but in this case I have no url to pass. What can I do to disable this configuration?

To reproduce

Langfuse self-hosted 3.29.1 OSS, langgraph = ">=0.2.62"

SDK and container versions

No response

Additional information

No response

Are you interested to contribute a fix for this bug?

Yes

[dosubot[bot]]

I found a similar unsolved discussion titled SDK-Python: Enable/Disable Media Upload which might be relevant to your issue ^[1].

To address the "Failed to get media upload URL" error in your self-hosted Langfuse setup, you can disable the media upload functionality by setting the environment variable LANGFUSE_S3_MEDIA_UPLOAD_ENABLED to false. This will disable multi-modal attachments without requiring code modifications ^[2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[juicechu]

It doesn't work. Because the upload process is control by python sdk. If set the env LANGFUSE_S3_MEDIA_UPLOAD_ENDPOINT to false, sdk will raise the error

langfuse._task_manager.media_manager:process_media_in_event:86 - Error processing multimodal event: status_code: 500, body: {'message': 'Failed to get media upload URL', 'error': 'InternalServerError'} - {}

[hassiebp]

@mrPsycox Is this happening in development? Could you please inspect your Langfuse server logs to see what exactly went wrong server side to create the upload URL?

Please see our docs on how media is handled in Langfuse: https://langfuse.com/docs/tracing-features/multi-modality#how-does-it-work

[mrPsycox]

hi @hassiebp, any news on that? Actually triggering this error, every multimodal output is dropped :(

[mrPsycox]

@hassiebp update on the issue. Seems that the langfuse handler sometimes save the traces, entering in minio I found these objects saved:

I've done some tries, and this totally random

[adityapnusantara]

@mrPsycox Is this happening in development? Could you please inspect your Langfuse server logs to see what exactly went wrong server side to create the upload URL?

Please see our docs on how media is handled in Langfuse: https://langfuse.com/docs/tracing-features/multi-modality#how-does-it-work

Any update regarding this?. i use cloud storage or minio get the same problem.

[luke6996]

I also face the same problem, is there any solution of this?

[mrPsycox]

My solution is to customize our langfuse to avoid to putting base64 in that.
Honestly, no other solutions worked.