mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-01 13:18:10 +00:00
* feat: adopt directory-based docs versioning with Edge channel Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>
207 lines
9.1 KiB
Plaintext
207 lines
9.1 KiB
Plaintext
---
|
|
title: MLflow 통합
|
|
description: MLflow를 사용하여 에이전트 모니터링을 빠르게 시작하세요.
|
|
icon: bars-staggered
|
|
mode: "wide"
|
|
---
|
|
|
|
# MLflow 개요
|
|
|
|
[MLflow](https://mlflow.org/)는 머신러닝 실무자와 팀이 머신러닝 프로세스의 복잡성을 관리할 수 있도록 돕는 오픈소스 플랫폼입니다.
|
|
|
|
MLflow는 귀하의 생성형 AI 애플리케이션에서 서비스 실행에 대한 상세 정보를 캡처하여 LLM 가시성을 향상시키는 트레이싱 기능을 제공합니다.
|
|
트레이싱은 요청의 각 중간 단계에 관련된 입력값, 출력값, 메타데이터를 기록하는 방법을 제공하여, 버그 및 예기치 않은 동작의 원인을 쉽게 찾아낼 수 있게 합니다.
|
|
|
|

|
|
|
|
### 기능
|
|
|
|
- **트레이싱 대시보드**: crewAI 에이전트의 활동을 입력값, 출력값, 스팬의 메타데이터와 함께 자세한 대시보드로 모니터링할 수 있습니다.
|
|
- **자동 트레이싱**: 완전 자동화된 crewAI 통합 기능으로, `mlflow.crewai.autolog()`를 실행하여 활성화할 수 있습니다.
|
|
- **약간의 노력만으로 수동 추적 계측**: 데코레이터, 함수 래퍼, 컨텍스트 매니저 등 MLflow의 고수준 fluent API를 통해 추적 계측을 커스터마이즈할 수 있습니다.
|
|
- **OpenTelemetry 호환성**: MLflow Tracing은 OpenTelemetry Collector로 트레이스를 내보내는 것을 지원하며, 이를 통해 Jaeger, Zipkin, AWS X-Ray 등 다양한 백엔드로 트레이스를 내보낼 수 있습니다.
|
|
- **에이전트 패키징 및 배포**: crewAI 에이전트를 다양한 배포 대상으로 추론 서버에 패키징 및 배포할 수 있습니다.
|
|
- **LLM을 안전하게 호스팅**: 여러 공급자의 LLM을 MFflow 게이트웨이를 통해 하나의 통합 엔드포인트에서 호스팅할 수 있습니다.
|
|
- **평가**: 편리한 API `mlflow.evaluate()`를 사용하여 다양한 지표로 crewAI 에이전트를 평가할 수 있습니다.
|
|
|
|
## 설치 안내
|
|
|
|
<Steps>
|
|
<Step title="MLflow 패키지 설치">
|
|
```shell
|
|
# crewAI 연동은 mlflow>=2.19.0 에서 사용할 수 있습니다.
|
|
pip install mlflow
|
|
```
|
|
</Step>
|
|
<Step title="MLflow 추적 서버 시작">
|
|
```shell
|
|
# 이 과정은 선택 사항이지만, MLflow 추적 서버를 사용하면 더 나은 시각화와 더 많은 기능을 사용할 수 있습니다.
|
|
mlflow server
|
|
```
|
|
</Step>
|
|
<Step title="애플리케이션에서 MLflow 초기화">
|
|
다음 두 줄을 애플리케이션 코드에 추가하세요:
|
|
|
|
```python
|
|
import mlflow
|
|
|
|
mlflow.crewai.autolog()
|
|
|
|
# 선택 사항: 추적 서버를 사용하는 경우 tracking URI와 experiment 이름을 설정할 수 있습니다.
|
|
mlflow.set_tracking_uri("http://localhost:5000")
|
|
mlflow.set_experiment("CrewAI")
|
|
```
|
|
|
|
CrewAI Agents 추적 예시 사용법:
|
|
|
|
```python
|
|
from crewai import Agent, Crew, Task
|
|
from crewai.knowledge.source.string_knowledge_source import StringKnowledgeSource
|
|
from crewai_tools import SerperDevTool, WebsiteSearchTool
|
|
|
|
from textwrap import dedent
|
|
|
|
content = "Users name is John. He is 30 years old and lives in San Francisco."
|
|
string_source = StringKnowledgeSource(
|
|
content=content, metadata={"preference": "personal"}
|
|
)
|
|
|
|
search_tool = WebsiteSearchTool()
|
|
|
|
|
|
class TripAgents:
|
|
def city_selection_agent(self):
|
|
return Agent(
|
|
role="City Selection Expert",
|
|
goal="Select the best city based on weather, season, and prices",
|
|
backstory="An expert in analyzing travel data to pick ideal destinations",
|
|
tools=[
|
|
search_tool,
|
|
],
|
|
verbose=True,
|
|
)
|
|
|
|
def local_expert(self):
|
|
return Agent(
|
|
role="Local Expert at this city",
|
|
goal="Provide the BEST insights about the selected city",
|
|
backstory="""A knowledgeable local guide with extensive information
|
|
about the city, it's attractions and customs""",
|
|
tools=[search_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
|
|
class TripTasks:
|
|
def identify_task(self, agent, origin, cities, interests, range):
|
|
return Task(
|
|
description=dedent(
|
|
f"""
|
|
Analyze and select the best city for the trip based
|
|
on specific criteria such as weather patterns, seasonal
|
|
events, and travel costs. This task involves comparing
|
|
multiple cities, considering factors like current weather
|
|
conditions, upcoming cultural or seasonal events, and
|
|
overall travel expenses.
|
|
Your final answer must be a detailed
|
|
report on the chosen city, and everything you found out
|
|
about it, including the actual flight costs, weather
|
|
forecast and attractions.
|
|
|
|
Traveling from: {origin}
|
|
City Options: {cities}
|
|
Trip Date: {range}
|
|
Traveler Interests: {interests}
|
|
"""
|
|
),
|
|
agent=agent,
|
|
expected_output="Detailed report on the chosen city including flight costs, weather forecast, and attractions",
|
|
)
|
|
|
|
def gather_task(self, agent, origin, interests, range):
|
|
return Task(
|
|
description=dedent(
|
|
f"""
|
|
As a local expert on this city you must compile an
|
|
in-depth guide for someone traveling there and wanting
|
|
to have THE BEST trip ever!
|
|
Gather information about key attractions, local customs,
|
|
special events, and daily activity recommendations.
|
|
Find the best spots to go to, the kind of place only a
|
|
local would know.
|
|
This guide should provide a thorough overview of what
|
|
the city has to offer, including hidden gems, cultural
|
|
hotspots, must-visit landmarks, weather forecasts, and
|
|
high level costs.
|
|
The final answer must be a comprehensive city guide,
|
|
rich in cultural insights and practical tips,
|
|
tailored to enhance the travel experience.
|
|
|
|
Trip Date: {range}
|
|
Traveling from: {origin}
|
|
Traveler Interests: {interests}
|
|
"""
|
|
),
|
|
agent=agent,
|
|
expected_output="Comprehensive city guide including hidden gems, cultural hotspots, and practical travel tips",
|
|
)
|
|
|
|
|
|
class TripCrew:
|
|
def __init__(self, origin, cities, date_range, interests):
|
|
self.cities = cities
|
|
self.origin = origin
|
|
self.interests = interests
|
|
self.date_range = date_range
|
|
|
|
def run(self):
|
|
agents = TripAgents()
|
|
tasks = TripTasks()
|
|
|
|
city_selector_agent = agents.city_selection_agent()
|
|
local_expert_agent = agents.local_expert()
|
|
|
|
identify_task = tasks.identify_task(
|
|
city_selector_agent,
|
|
self.origin,
|
|
self.cities,
|
|
self.interests,
|
|
self.date_range,
|
|
)
|
|
gather_task = tasks.gather_task(
|
|
local_expert_agent, self.origin, self.interests, self.date_range
|
|
)
|
|
|
|
crew = Crew(
|
|
agents=[city_selector_agent, local_expert_agent],
|
|
tasks=[identify_task, gather_task],
|
|
verbose=True,
|
|
memory=True,
|
|
knowledge={
|
|
"sources": [string_source],
|
|
"metadata": {"preference": "personal"},
|
|
},
|
|
)
|
|
|
|
result = crew.kickoff()
|
|
return result
|
|
|
|
|
|
trip_crew = TripCrew("California", "Tokyo", "Dec 12 - Dec 20", "sports")
|
|
result = trip_crew.run()
|
|
|
|
print(result)
|
|
```
|
|
더 많은 설정 및 사용 예시는 [MLflow Tracing 문서](https://mlflow.org/docs/latest/llms/tracing/index.html)를 참고하세요.
|
|
</Step>
|
|
<Step title="에이전트 활동 시각화">
|
|
이제 crewAI agents의 추적 정보가 MLflow에서 캡처됩니다.
|
|
MLflow 추적 서버에 접속하여 추적 내역을 확인하고 에이전트의 인사이트를 얻으세요.
|
|
|
|
브라우저에서 `127.0.0.1:5000`을 열어 MLflow 추적 서버에 접속하세요.
|
|
<Frame caption="MLflow 추적 대시보드">
|
|
<img src="/images/mlflow1.png" alt="MLflow tracing example with crewai" />
|
|
</Frame>
|
|
</Step>
|
|
</Steps>
|