Skip to content

Commit dfd6fd2

Browse files
committed
Add MLflow to tracing options
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
1 parent 397a363 commit dfd6fd2

File tree

1 file changed

+5
-4
lines changed
  • docs/user-guide/observability-evaluation

1 file changed

+5
-4
lines changed

docs/user-guide/observability-evaluation/traces.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -239,9 +239,10 @@ Traces can be visualized and analyzed using any OpenTelemetry-compatible tool:
239239
Common visualization options include:
240240

241241
1. **Jaeger**: Open-source, end-to-end distributed tracing
242-
2. **Langfuse**: For Traces, evals, prompt management, and metrics
243-
3. **AWS X-Ray**: For AWS-based applications
244-
4. **Zipkin**: Lightweight distributed tracing
242+
2. **MLflow**: Open-source LLMOps platform for tracing and evaluation.
243+
3. **Langfuse**: For Traces, evals, prompt management, and metrics
244+
4. **AWS X-Ray**: For AWS-based applications
245+
5. **Zipkin**: Lightweight distributed tracing
245246

246247
## Local Development Setup
247248

@@ -393,4 +394,4 @@ print(response)
393394
There are several ways to send traces, metrics, and logs to CloudWatch. Please visit the following pages for more details and configurations:
394395
1. [AWS Distro for OpenTelemetry Collector](https://aws-otel.github.io/docs/getting-started/x-ray#configuring-the-aws-x-ray-exporter)
395396
2. [AWS CloudWatch OpenTelemetry User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-OpenTelemetry-Sections.html)
396-
- Please ensure Transaction Search is enabled in CloudWatch.
397+
- Please ensure Transaction Search is enabled in CloudWatch.

0 commit comments

Comments
 (0)