Skip to content

disable litellm debug messages for databricks models#21082

Merged
bbqiu merged 9 commits intomlflow:masterfrom
bbqiu:bbqiu/litellm-suppression
Feb 24, 2026
Merged

disable litellm debug messages for databricks models#21082
bbqiu merged 9 commits intomlflow:masterfrom
bbqiu:bbqiu/litellm-suppression

Conversation

@bbqiu
Copy link
Collaborator

@bbqiu bbqiu commented Feb 23, 2026

Related Issues/PRs

#xxx

What changes are proposed in this pull request?

slack thread context: https://databricks.slack.com/archives/C022KUWGVQS/p1771842499541559

when using autologging with a Databricks LLM, logs like the following are being printed: Provider List: https://docs.litellm.ai/docs/providers. this PR disables those messages when using a databricks LLM by default, as it is unintuitive to end users why they're getting a litellm message when nothing in their code uses litellm.

How is this PR tested?

  • Existing unit/integration tests
  • New unit/integration tests
  • Manual tests

before in logs:
also after when MLflow logging is set to DEBUG:

Provider List: https://docs.litellm.ai/docs/providers

after: no unexpected logs

Does this PR require documentation update?

  • No. You can skip the rest of this section.
  • Yes. I've updated:
    • Examples
    • API references
    • Instructions

Does this PR require updating the MLflow Skills repository?

  • No. You can skip the rest of this section.
  • Yes. Please link the corresponding PR or explain how you plan to update it.

Release Notes

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

  • area/tracking: Tracking Service, tracking client APIs, autologging
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
  • area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
  • area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
  • area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
  • area/projects: MLproject format, project running backends
  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/build: Build and test infrastructure for MLflow
  • area/docs: MLflow documentation pages

How should the PR be classified in the release notes? Choose one:

  • rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.

What is a minor/patch release?
  • Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
    Bug fixes, doc updates and new features usually go into minor releases.
  • Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
    Bug fixes and doc updates usually go into patch releases.
  • Yes (this PR will be cherry-picked and included in the next patch release)
  • No (this PR will be included in the next minor release)

.
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
@github-actions
Copy link
Contributor

🛠 DevTools 🛠

Install mlflow from this PR

# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/21082/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/21082/merge#subdirectory=libs/skinny

For Databricks, use the following command:

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/21082/merge

.
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
@github-actions github-actions bot added v3.10.1 area/tracing MLflow Tracing and its integrations rn/none List under Small Changes in Changelogs. labels Feb 23, 2026
@bbqiu bbqiu changed the title . disable litellm debug messages for databricks models Feb 23, 2026
@github-actions github-actions bot removed area/tracing MLflow Tracing and its integrations rn/none List under Small Changes in Changelogs. labels Feb 23, 2026
@bbqiu bbqiu requested a review from daniellok-db February 23, 2026 20:11
@github-actions github-actions bot added area/tracing MLflow Tracing and its integrations rn/none List under Small Changes in Changelogs. labels Feb 23, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 23, 2026

Documentation preview for 8e412e3 is available at:

More info
  • Ignore this comment if this PR does not change the documentation.
  • The preview is updated when a new commit is pushed to this PR.
  • This comment was created by this workflow run.
  • The documentation was built by this workflow run.

.
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
.
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
.
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
.
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
Copy link
Collaborator

@serena-ruan serena-ruan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after comments are addressed! Thanks for fixing this!

.
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
.
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
@bbqiu bbqiu enabled auto-merge February 24, 2026 18:08
@bbqiu bbqiu added this pull request to the merge queue Feb 24, 2026
Merged via the queue into mlflow:master with commit 374eb7e Feb 24, 2026
58 checks passed
@bbqiu bbqiu deleted the bbqiu/litellm-suppression branch February 24, 2026 18:55
@github-actions github-actions bot added size/S Small PR (10-49 LoC) and removed size/M labels Feb 24, 2026
smoorjani pushed a commit to smoorjani/mlflow that referenced this pull request Feb 26, 2026
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
Signed-off-by: Samraj Moorjani <samraj.moorjani@databricks.com>
daniellok-db pushed a commit to daniellok-db/mlflow that referenced this pull request Mar 5, 2026
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
daniellok-db pushed a commit to daniellok-db/mlflow that referenced this pull request Mar 5, 2026
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
daniellok-db pushed a commit that referenced this pull request Mar 5, 2026
Signed-off-by: bbqiu <bryan.qiu@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/tracing MLflow Tracing and its integrations rn/none List under Small Changes in Changelogs. size/S Small PR (10-49 LoC) v3.10.1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants