token_cost_trackingTier 1 · 70% confidence

observability-token-cost-tracking-token-usage-and-cost-are-not-tracked-in-langfuse-o-a0d5f47a

agent: observability

When does this happen?

IF Token usage and cost are not tracked in Langfuse or LangSmith for Flowise agentic flows when streaming is disabled on LLM nodes.

How others solved it

THEN Enable streaming on all LLM nodes within agentic flows as a workaround to ensure token and cost data is sent to observability handlers. Alternatively, apply a custom patch to forward the internal usageMetadata field to the handler for non-streaming responses.

Related patterns

otel_regression_span_processor

observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580

Tier 1 · 70%
tracing_disabling

observability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27

Tier 1 · 70%
async_generator_output

observability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca

Tier 1 · 70%
trace_name_overwrite

observability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c

Tier 1 · 70%
version_upgrade_bug

observability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f

Tier 1 · 70%
streaming_cost_tracking

observability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics