Python: add MLflow to the observability backend examples - #8085
Open
NekoPunch (orangeCatDeveloper) wants to merge 1 commit into
Open
Python: add MLflow to the observability backend examples#8085NekoPunch (orangeCatDeveloper) wants to merge 1 commit into
NekoPunch (orangeCatDeveloper) wants to merge 1 commit into
Conversation
NekoPunch (orangeCatDeveloper)
deployed
to
github-app-auth
September 5, 2026 04:18 — with
GitHub Actions
Active
NekoPunch (orangeCatDeveloper)
deployed
to
github-app-auth
September 5, 2026 04:18 — with
GitHub Actions
Active
NekoPunch (orangeCatDeveloper)
deployed
to
github-app-auth
September 5, 2026 04:19 — with
GitHub Actions
Active
Copilot started reviewing on behalf of
NekoPunch (orangeCatDeveloper)
September 5, 2026 04:19
View session
NekoPunch (orangeCatDeveloper)
deployed
to
github-app-auth
September 5, 2026 04:19 — with
GitHub Actions
Active
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The example matches the framework API and MLflow’s documented tracing configuration.
Pull request overview
Adds MLflow as a documented OpenTelemetry tracing backend for Python Agent Framework samples.
Changes:
- Documents MLflow’s OTLP/HTTP trace endpoint and experiment header.
- Demonstrates configuring a trace-only exporter and optional sensitive telemetry.
File summaries
| File | Description |
|---|---|
python/samples/02-agents/observability/README.md |
Adds the MLflow setup example. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #7769
Motivation & Context
The observability README shows how to point Agent Framework at Langfuse and Comet Opik, but not MLflow, which is a common OTel-based backend. MLflow accepts only traces at
<tracking-uri>/v1/traces, so users who copy the baseOTEL_EXPORTER_OTLP_ENDPOINTpattern also get log and metric exporters retrying against endpoints MLflow does not serve. A section with the right shape saves that detour.Description & Review Guide
Adds an MLflow entry next to the Langfuse and Opik ones in
python/samples/02-agents/observability/README.md. It passes a singleOTLPSpanExporter(HTTP) with thex-mlflow-experiment-idheader viaconfigure_otel_providers(exporters=[...]), which is the same shape as pattern 2 in that README and as MLflow's own integration page, only using the currentconfigure_otel_providers/enable_sensitive_telemetrynames instead of the oldersetup_observabilitythe MLflow docs still show.Only the GitHub README half of the issue is covered here; the learn-site update is left to the maintainers since that repository is mid-migration.
Verified against a local MLflow 3.16.0 server with the snippet verbatim, driving a real
Agentwith an echo chat client:Contribution Checklist