Solution skill
Otel reporting does not include input/output values
Complete solution
Shows how to fix otel reporting does not include input/output values. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
With a console span exporter the attributes input.value/output.value are visibly set, but Langfuse shows empty input/output on the trace.
Steps
- Native OTel reporting loses input/output values in Langfuse. With a console span exporter the attributes
input.value/output.valueare visibly set, but Langfuse shows empty input/output on the trace. - Two concrete findings came out of the thread (maintainers hassiebp and Steffen911): (1) in Next.js 14 the span processor may never flush inside serverless functions, Next 15's
after()(not Next 14'swaitUntil) is the recommended place to schedule the Langfuse flush, andexportMode: 'immediate'on LangfuseSpanProcessor forces immediate export; (2)langfuse-vercelis deprecated, maintainer hassiebp confirmed it and the docs were updated to point at the @langfuse/otel-based integration.
When to use
You are seeing this: Native OTel reporting loses input/output values in Langfuse. Use this skill when you run into "Otel reporting does not include input/output values".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
In gh:langfuse/langfuse#5971 (https://github.com/langfuse/langfuse/issues/5971), the question was: Native OTel reporting loses input/output values in Langfuse. With a console span exporter the attributes input.value/output.value are visibly set, but Langfuse shows empty input/output on the trace. The verified resolution: Two concrete findings came out of the thread (maintainers hassiebp and Steffen911): (1) in Next.js 14 the span processor may never flush inside serverless functions, Next 15's after() (not Next 14's waitUntil) is the recommended place to schedule the Langfuse flush, and exportMode: 'immediate' on LangfuseSpanProcessor forces immediate export; (2) langfuse-vercel is deprecated, maintainer hassiebp confirmed it and the docs were updated to point at the @langfuse/otel-based integration.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_aSgZjNVzKXhVVJW3_2V4ug" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Otel reporting does not include input/output values <span>— Vectle</span></a>