ladislas14
LLangfuse
•Created by James Coates on 3/6/2024 in #feature-suggestion
Hey. Firstly thank you for all the work
I think the need might be different between self-hosted and cloud.
In my case where we are self-hosting Langfuse, our need is mostly to be able to hide the data to certain users, but let them see the trace, the usage, etc.
9 replies
LLangfuse
•Created by James Coates on 3/6/2024 in #feature-suggestion
Hey. Firstly thank you for all the work
You mean the tokencounts/cost tracking will not be infered but it can still be ingested no ?
9 replies
LLangfuse
•Created by James Coates on 3/6/2024 in #feature-suggestion
Hey. Firstly thank you for all the work
That's a good question.
Wouldn't be possible to have a more granular role control. I think it would be nice to be able to hide the inputs/outputs in Langfuse for a specific role (quite like the current Viewer role)
9 replies
LLangfuse
•Created by James Coates on 3/6/2024 in #feature-suggestion
Hey. Firstly thank you for all the work
Hi, I actually had the same issue yesterday and end up forking the Langchain
CallbackHandler and removing the input and output in the created observations.
This is not perfect and I think there is a better way to do it.
I would be pleased to know if there is something planned in the roadmap about data anonymisation !
For the moment, if you need, I can share what I've done with the CallbackHandler9 replies