I have searched the existing issues and discussions.
Problem Description
In order to track the whole cost of an LLM using tools, we need get this tools in the inlet function of pipelines.
This would be extremely useful for debugging too. I'd make the PR, but I don't think there is a way to see all the available tools.
Desired Solution you'd like
Using langfuse pipeline, we are able to track the whole call to the LLM (user query, available tools, llm answer, tool answers...)
Alternatives Considered
No response
Additional Context
No response
Originally created by @juan-abia on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12565
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
In order to track the whole cost of an LLM using tools, we need get this tools in the inlet function of pipelines.
This would be extremely useful for debugging too. I'd make the PR, but I don't think there is a way to see all the available tools.
### Desired Solution you'd like
Using langfuse pipeline, we are able to track the whole call to the LLM (user query, available tools, llm answer, tool answers...)
### Alternatives Considered
_No response_
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @juan-abia on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12565
Check Existing Issues
Problem Description
In order to track the whole cost of an LLM using tools, we need get this tools in the inlet function of pipelines.
This would be extremely useful for debugging too. I'd make the PR, but I don't think there is a way to see all the available tools.
Desired Solution you'd like
Using langfuse pipeline, we are able to track the whole call to the LLM (user query, available tools, llm answer, tool answers...)
Alternatives Considered
No response
Additional Context
No response