From c6ebed2b4e73cb5cbfcba95852e3ed5bc1297704 Mon Sep 17 00:00:00 2001 From: B-Step62 Date: Wed, 26 Nov 2025 00:26:57 +0900 Subject: [PATCH] Add MLflow to tracing options Signed-off-by: B-Step62 --- docs/user-guide/observability-evaluation/traces.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/user-guide/observability-evaluation/traces.md b/docs/user-guide/observability-evaluation/traces.md index d812238a..5d909762 100644 --- a/docs/user-guide/observability-evaluation/traces.md +++ b/docs/user-guide/observability-evaluation/traces.md @@ -239,9 +239,10 @@ Traces can be visualized and analyzed using any OpenTelemetry-compatible tool: Common visualization options include: 1. **Jaeger**: Open-source, end-to-end distributed tracing -2. **Langfuse**: For Traces, evals, prompt management, and metrics -3. **AWS X-Ray**: For AWS-based applications -4. **Zipkin**: Lightweight distributed tracing +2. **MLflow**: [Open-source](https://github.com/mlflow/mlflow/tree/master) LLMOps platform for tracing and evaluation. Managed version is available in [SageMaker AI](https://aws.amazon.com/jp/sagemaker/ai/experiments/). +3. **Langfuse**: For Traces, evals, prompt management, and metrics +4. **AWS X-Ray**: For AWS-based applications +5. **Zipkin**: Lightweight distributed tracing ## Local Development Setup