langfuse
[LFC-192] OpenTelemetry
OTel as (1) additional data source for more execution details, and (2) alternative integration to replace current SDKs
Did you all make a decision regarding OTel integration? My team at Microsoft is curious (since Azure Monitor brings in OTel traces).
Currently we see otel to be promising for some of our users (just monitor/log production traffic), whereas it does not work for others (also want to quickly iterate locally / in batches / in notebooks). Thus, we cannot yet shift all of our tracing/ingestion to OTel.
The best way forward here is most likely to build an OTel compatible receiver/processor as an alternative way to ingest data into langfuse for those who want it for their production deployments.
As generally building integrations for Langfuse is very simple, we are very open to collab on this, right now, there are higher impact features to ship for most of our users especially with a focus on evaluation and testing of LLM applications.
If you have a view on this, happy to chat with you and your team!
Okay, that makes sense. I don't have a strong opinion currently, I'll look out for feedback from our Microsoft customers.
Hi @marcklingen, it's great to know that you're thinking about integrating OTEL into Langfuse.
A new Working Group (WG) was formed recently as part of the OpenTelemetry Semantic Conventions project, with a specific focus on LLM applications and frameworks.
If you're interested, I'd like to extend an invitation for you to join our community meeting. You can share any insights you have from your experience with OTEL adoption and provide feedback on the conventions we're developing for this project.
LLM Semantic Conventions Working Goup OTEL Semantic Conventions Sigs Index Slack Channel
@drewby @pamelafox
I would also love to see support of OpenTelemetry ingestion. My specific reason would be to enable observablity of Semantic Kernel based applications in langfuse. It would be awesome if we could see the single steps of SK applications in the same way we can currently see langchain-based application traces.
I'd also love to see support in some kind for this - in particular, I'd love to be able to incorporate (or leverage) Langfuse tracing as part of broader application tracing, and send those traces through an OpenTelemetry Collector rather than directly to LANGFUSE_HOST
Is this something that has been tested or attempted previously with any success?
Also interested in this feature - my (customers') use-case would be similar to the above: Integrate Langfuse's traces with those from other microservices/apps in AWS X-Ray, for end-to-end debugging & visibility.
When it comes to Langfuse ingesting OpenTelemetry, I think it is more straightforward to implement an OpenTelemetry exporter that calls Langfuse SDK for each OpenTelemetry trace.
