Tool calling costs are currently ignored

[xdivby0]

Describe your question

Currently all costs inside an observation that is not a generation or embedding type is just ignored. It would be so helpful (and probably not break anything) if the trace total cost also could include the costDetails.total value of tool call spans.

I am sure I am not alone with the fact that many APIs that an agent could call are paid and therefore it would be nice to see what an average trace (or any given specific trace) cost me. Am I overlooking anything?

There was also an open issue / discussion about doing aggregations with custom metadata. This might be an alternative solution if langfuse does not see this as a common enough use case.

Langfuse Cloud or Self-Hosted?

Langfuse Cloud

If Self-Hosted

No response

If Langfuse Cloud

No response

SDK and integration versions

No response

Pre-Submission Checklist

• I have checked for existing issues/discussions and consulted Langfuse AI.

[jannikmaierhoefer]

Thanks @xdivby0, yes, currently only observations of type "generation" and "embedding" support costs. We have it on our roadmap to also allow this for other observation types and allow more flexibility in the cost calculation model.

[itxashancode]

I’ve looked at the current schema - tool calls come in as observations of type SPAN (or TOOL in some SDKs) and the cost field is only populated for GENERATION and EMB E.