Skip to content

Add 2026-06-llmops-quickstart blog code - #91

Open
CEDipEngineering wants to merge 3 commits into
databricks-solutions:mainfrom
CEDipEngineering:add-2026-06-llmops-quickstart
Open

Add 2026-06-llmops-quickstart blog code#91
CEDipEngineering wants to merge 3 commits into
databricks-solutions:mainfrom
CEDipEngineering:add-2026-06-llmops-quickstart

Conversation

@CEDipEngineering

@CEDipEngineering CEDipEngineering commented Jun 5, 2026

Copy link
Copy Markdown

What this is

End-to-end LLMOps quickstart on Databricks — a customer support ticket classifier
that carries an LLM agent through the full lifecycle: data ingestion → agent build →
evaluation → approval → governed deployment → batch + real-time inference.

Accompanies an upcoming Databricks Community blog post (JIRA TLC-1077).

Contents

  • New folder 2026-06-llmops-quickstart/ (follows the YYYY-MM-[name] convention)
  • MLflow ChatAgent on a Foundation Model API endpoint (default databricks-claude-sonnet-5)
  • A Databricks Asset Bundle deploying schema, experiment, and jobs (dev/prod targets)
  • Extensive README.md (setup, structure, prerequisites, governance notes, "before you call it done" checklist, blog-link placeholder)
  • LICENSE.md — unmodified copy of the repo's Databricks license
  • CODEOWNERS entry added for the new folder

2026 LLMOps building blocks

This quickstart mirrors the pragmatic, step-by-step shape of the MLOps Quickstart, adapted for LLM apps with current (2026) tooling:

  • MLflow 3 GenAI evaluationmlflow.genai.evaluate() with a deterministic exact_match gate scorer plus the built-in Correctness LLM judge; every prediction captured as an MLflow Trace.
  • Challenger → Champion with a human approval gate — passing versions register as Challenger; model_approval.py promotes to Champion only when run with --params approved=true, wired as a predecessor to deployment.
  • Unity AI Gateway — payload logging to a Delta inference table enabled on the served endpoint for audit/monitoring. Guardrails and rate limits are documented as a foundation-model-endpoint pattern (they don't attach to custom agent endpoints).
  • Reasoning-model-safe agent — response content is normalized so reasoning models (Claude Sonnet 5, GPT-5) that return structured content blocks work, not just plain-string responses.

Testing

Deployed and run end-to-end from scratch on three separate workspaces (two AWS, one Azure): bundle deploy → all four jobs → approval → governed endpoint → batch + real-time inference all verified green. Portability notes (e.g. the serverless runtime identity's Unity Catalog privileges) are captured in the README prerequisites.

Guidelines checklist

  • I have read the contribution guidelines
  • No sensitive information / no secrets (CI pipelines referencing SP secrets were excluded)
  • No PII; no external dataset (only 30 small, hand-written synthetic tickets)
  • Licenses listed in the README; Databricks license unchanged
  • Folder renamed to YYYY-MM-[folder_name]
  • Added myself to CODEOWNERS
  • Domain SME has reviewed the code and approved in a PR comment (pending)

Blog post link will be added to the README once published.

This pull request and its description were written by Isaac.

End-to-end LLMOps quickstart on Databricks (customer support ticket
classifier): MLflow ChatAgent on a Foundation Model API endpoint, an
evaluation gate that promotes a Champion in Unity Catalog, and a
Databricks Asset Bundle that deploys schema, experiment, and jobs with
batch + real-time inference.

- Folder follows the YYYY-MM-[name] convention
- README documents setup, structure, data (30 synthetic tickets, no PII), and licenses
- LICENSE.md is an unmodified copy of the repo Databricks license
- CODEOWNERS entry added for the new folder

I have read the contribution guidelines. No sensitive info, no PII, no
external dataset. Pending: SME code review approval and internal approval.

Co-authored-by: Isaac
CEDipEngineering and others added 2 commits June 5, 2026 16:13
…al, AI Gateway logging

Bring the quickstart current (2026) and align it with the MLOps quickstart's
step-by-step, best-practices structure. Tested end-to-end across three workspaces
(deploy → 4 jobs → approval → governed endpoint → batch + realtime).

- Evaluation: replace the hand-rolled accuracy loop with mlflow.genai.evaluate()
  using a deterministic exact_match gate scorer plus the built-in Correctness LLM
  judge; every row is captured as an MLflow Trace.
- Lifecycle: passing versions register as Challenger; new model_approval.py promotes
  Challenger→Champion only when run with --params approved=true, wired as a
  predecessor task to deployment.
- Governance: after agents.deploy(), enable AI Gateway inference-table payload logging
  on the agent endpoint (idempotent). Guardrails/rate limits documented as an
  FM-endpoint pattern (not supported on custom agent endpoints).
- Agent: normalize response content so reasoning models (Claude Sonnet 5, GPT-5) that
  return structured content blocks work, not just plain-string responses.
- Default LLM endpoint → databricks-claude-sonnet-5; pin mlflow>=3.4.0 in the logged model.
- Harden stale-deployment cleanup; README updated with the new flow, approval gate,
  governance notes, UC-privilege prerequisite, and a "before you call it done" checklist.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant