From ef0d58c7e82e6572b3a43b6cce50fa44a734b8b8 Mon Sep 17 00:00:00 2001 From: Marc Klingen Date: Mon, 3 Feb 2025 21:00:40 +0100 Subject: [PATCH 1/2] docs: add link to otel docs to otel blog post --- .../2024-10-opentelemetry-for-llm-observability.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/pages/blog/2024-10-opentelemetry-for-llm-observability.mdx b/pages/blog/2024-10-opentelemetry-for-llm-observability.mdx index 8a628deb7..17d6c6942 100644 --- a/pages/blog/2024-10-opentelemetry-for-llm-observability.mdx +++ b/pages/blog/2024-10-opentelemetry-for-llm-observability.mdx @@ -18,6 +18,12 @@ import { BlogHeader } from "@/components/blog/BlogHeader"; import Image from "next/image"; + + +**Update**: We have released a [Langfuse OTel Collector](/docs/opentelemetry/get-started) to icnrease compatibility with emerging OTel-based instrumentation libraries. + + + ## Introduction to OpenTelemetry Logo [OpenTelemetry](https://opentelemetry.io/) is an open-source observability framework designed to handle the instrumentation of applications for collecting traces, metrics, and logs. It helps developers monitor and troubleshoot complex systems by providing standardized tools and practices for data collection and analysis. @@ -129,6 +135,12 @@ We are committed to OTel and are happy to contribute to the SIG. We will continu Discussion thread](https://github.com/orgs/langfuse/discussions/2509). + + +**Update**: We have released a [Langfuse OTel Collector](/docs/opentelemetry/get-started) to icnrease compatibility with emerging OTel-based instrumentation libraries. + + + ## Get Started If you want to get started with tracing your AI applications with Langfuse today, check out our [quickstart guide](/docs/get-started) on how to use Langfuse with multiple LLM building frameworks like [Langchain](/docs/integrations/langchain/tracing) or [LlamaIndex](/docs/integrations/llama-index/get-started). From b2ad3c8633ac08275863f55cc333b349cffad35d Mon Sep 17 00:00:00 2001 From: "ellipsis-dev[bot]" <65095814+ellipsis-dev[bot]@users.noreply.github.com> Date: Mon, 3 Feb 2025 21:38:43 +0100 Subject: [PATCH 2/2] address comments left by @marcklingen on #1231 (docs: add link to otel docs to otel blog post); (#1232) Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com> --- pages/blog/2024-10-opentelemetry-for-llm-observability.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/blog/2024-10-opentelemetry-for-llm-observability.mdx b/pages/blog/2024-10-opentelemetry-for-llm-observability.mdx index 17d6c6942..8dafae8ae 100644 --- a/pages/blog/2024-10-opentelemetry-for-llm-observability.mdx +++ b/pages/blog/2024-10-opentelemetry-for-llm-observability.mdx @@ -20,7 +20,7 @@ import Image from "next/image"; -**Update**: We have released a [Langfuse OTel Collector](/docs/opentelemetry/get-started) to icnrease compatibility with emerging OTel-based instrumentation libraries. +**Update**: We have released a [Langfuse OTel Collector](/docs/opentelemetry/get-started) to increase compatibility with emerging OTel-based instrumentation libraries. @@ -137,7 +137,7 @@ We are committed to OTel and are happy to contribute to the SIG. We will continu -**Update**: We have released a [Langfuse OTel Collector](/docs/opentelemetry/get-started) to icnrease compatibility with emerging OTel-based instrumentation libraries. +**Update**: We have released a [Langfuse OTel Collector](/docs/opentelemetry/get-started) to increase compatibility with emerging OTel-based instrumentation libraries.