If Data/Metadata given to Langfuse SDK that exceeds Langfuse's limit, log/throw/emit Stack Trace

[josiahbryan]

Describe the feature or potential improvement

When .update or .end called (nodejs sdk) with data that is "too large" (>1MB), could you (a) emit an event with a stack trace so I can figure out where it originated in my code or (b) log to console with a stack trace or (c) throw an Error?

Right now, current behavior of logging a warning to process.stdout via console.log saying Item exceeds... is so generic and gives zero hints as to where the data is coming from. In a codebase that is >500K SLOC, that is not fun to hunt down, even with the debug() turned on.

Adding an explicit event or error or log at point-of-origin of the "big data" problem (e.g. where it goes from my code to your library) would signicantly speed up the fixing of any future such problems.

Additional information

Discord thread: https://discord.com/channels/1111061815649124414/1257496010419339395

Posted in #feature-suggestions on Discord too: https://discord.com/channels/1111061815649124414/1111063505563562064/1259890288671854653

[marcklingen]

thanks for raising this! cc @hassiebp who might appreciate the discussion on this