mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-01 21:28: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>
232 lines
8.0 KiB
Plaintext
232 lines
8.0 KiB
Plaintext
---
|
||
title: "Maxim Integration"
|
||
description: "Start Agent monitoring, evaluation, and observability"
|
||
icon: "infinity"
|
||
mode: "wide"
|
||
---
|
||
|
||
# Maxim Overview
|
||
|
||
Maxim AI provides comprehensive agent monitoring, evaluation, and observability for your CrewAI applications. With Maxim's one-line integration, you can easily trace and analyse agent interactions, performance metrics, and more.
|
||
|
||
## Features
|
||
|
||
### Prompt Management
|
||
|
||
Maxim's Prompt Management capabilities enable you to create, organize, and optimize prompts for your CrewAI agents. Rather than hardcoding instructions, leverage Maxim’s SDK to dynamically retrieve and apply version-controlled prompts.
|
||
|
||
<Tabs>
|
||
<Tab title="Prompt Playground">
|
||
Create, refine, experiment and deploy your prompts via the playground. Organize of your prompts using folders and versions, experimenting with the real world cases by linking tools and context, and deploying based on custom logic.
|
||
|
||
Easily experiment across models by [**configuring models**](https://www.getmaxim.ai/docs/introduction/quickstart/setting-up-workspace#add-model-api-keys) and selecting the relevant model from the dropdown at the top of the prompt playground.
|
||
|
||
<img src='https://raw.githubusercontent.com/akmadan/crewAI/docs_maxim_observability/docs/images/maxim_playground.png'> </img>
|
||
</Tab>
|
||
<Tab title="Prompt Versions">
|
||
As teams build their AI applications, a big part of experimentation is iterating on the prompt structure. In order to collaborate effectively and organize your changes clearly, Maxim allows prompt versioning and comparison runs across versions.
|
||
|
||
<img src='https://raw.githubusercontent.com/akmadan/crewAI/docs_maxim_observability/docs/images/maxim_versions.png'> </img>
|
||
</Tab>
|
||
<Tab title="Prompt Comparisons">
|
||
Iterating on Prompts as you evolve your AI application would need experiments across models, prompt structures, etc. In order to compare versions and make informed decisions about changes, the comparison playground allows a side by side view of results.
|
||
|
||
## **Why use Prompt comparison?**
|
||
|
||
Prompt comparison combines multiple single Prompts into one view, enabling a streamlined approach for various workflows:
|
||
|
||
1. **Model comparison**: Evaluate the performance of different models on the same Prompt.
|
||
2. **Prompt optimization**: Compare different versions of a Prompt to identify the most effective formulation.
|
||
3. **Cross-Model consistency**: Ensure consistent outputs across various models for the same Prompt.
|
||
4. **Performance benchmarking**: Analyze metrics like latency, cost, and token count across different models and Prompts.
|
||
</Tab>
|
||
</Tabs>
|
||
|
||
### Observability & Evals
|
||
|
||
Maxim AI provides comprehensive observability & evaluation for your CrewAI agents, helping you understand exactly what's happening during each execution.
|
||
|
||
<Tabs>
|
||
<Tab title="Agent Tracing">
|
||
Track your agent’s complete lifecycle, including tool calls, agent trajectories, and decision flows effortlessly.
|
||
|
||
<img src='https://raw.githubusercontent.com/akmadan/crewAI/docs_maxim_observability/docs/images/maxim_agent_tracking.png'> </img>
|
||
</Tab>
|
||
<Tab title="Analytics + Evals">
|
||
Run detailed evaluations on full traces or individual nodes with support for:
|
||
|
||
- Multi-step interactions and granular trace analysis
|
||
- Session Level Evaluations
|
||
- Simulations for real-world testing
|
||
|
||
<img src='https://raw.githubusercontent.com/akmadan/crewAI/docs_maxim_observability/docs/images/maxim_trace_eval.png'> </img>
|
||
|
||
<CardGroup cols={3}>
|
||
<Card title="Auto Evals on Logs" icon="e" href="https://www.getmaxim.ai/docs/observe/how-to/evaluate-logs/auto-evaluation">
|
||
<p>
|
||
Evaluate captured logs automatically from the UI based on filters and sampling
|
||
|
||
</p>
|
||
</Card>
|
||
<Card title="Human Evals on Logs" icon="hand" href="https://www.getmaxim.ai/docs/observe/how-to/evaluate-logs/human-evaluation">
|
||
<p>
|
||
Use human evaluation or rating to assess the quality of your logs and evaluate them.
|
||
|
||
</p>
|
||
</Card>
|
||
<Card title="Node Level Evals" icon="road" href="https://www.getmaxim.ai/docs/observe/how-to/evaluate-logs/node-level-evaluation">
|
||
<p>
|
||
Evaluate any component of your trace or log to gain insights into your agent’s behavior.
|
||
|
||
</p>
|
||
</Card>
|
||
</CardGroup>
|
||
---
|
||
</Tab>
|
||
<Tab title="Alerting">
|
||
Set thresholds on **error**, **cost, token usage, user feedback, latency** and get real-time alerts via Slack or PagerDuty.
|
||
|
||
<img src='https://raw.githubusercontent.com/akmadan/crewAI/docs_maxim_observability/docs/images/maxim_alerts_1.png'> </img>
|
||
</Tab>
|
||
<Tab title="Dashboards">
|
||
Visualize Traces over time, usage metrics, latency & error rates with ease.
|
||
|
||
<img src='https://raw.githubusercontent.com/akmadan/crewAI/docs_maxim_observability/docs/images/maxim_dashboard_1.png'> </img>
|
||
</Tab>
|
||
</Tabs>
|
||
|
||
## Getting Started
|
||
|
||
### Prerequisites
|
||
|
||
|
||
- Python version \>=3.10
|
||
- A Maxim account ([sign up here](https://getmaxim.ai/))
|
||
- Generate Maxim API Key
|
||
- A CrewAI project
|
||
|
||
### Installation
|
||
|
||
Install the Maxim SDK via pip:
|
||
|
||
```python
|
||
pip install maxim-py
|
||
```
|
||
|
||
Or add it to your `requirements.txt`:
|
||
|
||
```
|
||
maxim-py
|
||
```
|
||
### Basic Setup
|
||
|
||
### 1. Set up environment variables
|
||
|
||
```python
|
||
### Environment Variables Setup
|
||
|
||
# Create a `.env` file in your project root:
|
||
|
||
# Maxim API Configuration
|
||
MAXIM_API_KEY=your_api_key_here
|
||
MAXIM_LOG_REPO_ID=your_repo_id_here
|
||
```
|
||
|
||
### 2. Import the required packages
|
||
|
||
```python
|
||
from crewai import Agent, Task, Crew, Process
|
||
from maxim import Maxim
|
||
from maxim.logger.crewai import instrument_crewai
|
||
```
|
||
|
||
### 3. Initialise Maxim with your API key
|
||
|
||
|
||
```python {8}
|
||
# Instrument CrewAI with just one line
|
||
instrument_crewai(Maxim().logger())
|
||
```
|
||
|
||
### 4. Create and run your CrewAI application as usual
|
||
|
||
```python
|
||
# Create your agent
|
||
researcher = Agent(
|
||
role='Senior Research Analyst',
|
||
goal='Uncover cutting-edge developments in AI',
|
||
backstory="You are an expert researcher at a tech think tank...",
|
||
verbose=True,
|
||
llm=llm
|
||
)
|
||
|
||
# Define the task
|
||
research_task = Task(
|
||
description="Research the latest AI advancements...",
|
||
expected_output="",
|
||
agent=researcher
|
||
)
|
||
|
||
# Configure and run the crew
|
||
crew = Crew(
|
||
agents=[researcher],
|
||
tasks=[research_task],
|
||
verbose=True
|
||
)
|
||
|
||
try:
|
||
result = crew.kickoff()
|
||
finally:
|
||
maxim.cleanup() # Ensure cleanup happens even if errors occur
|
||
```
|
||
|
||
|
||
That's it\! All your CrewAI agent interactions will now be logged and available in your Maxim dashboard.
|
||
|
||
Check this Google Colab Notebook for a quick reference - [Notebook](https://colab.research.google.com/drive/1ZKIZWsmgQQ46n8TH9zLsT1negKkJA6K8?usp=sharing)
|
||
|
||
## Viewing Your Traces
|
||
|
||
After running your CrewAI application:
|
||
|
||
1. Log in to your [Maxim Dashboard](https://app.getmaxim.ai/login)
|
||
2. Navigate to your repository
|
||
3. View detailed agent traces, including:
|
||
- Agent conversations
|
||
- Tool usage patterns
|
||
- Performance metrics
|
||
- Cost analytics
|
||
|
||
<img src='https://raw.githubusercontent.com/akmadan/crewAI/docs_maxim_observability/docs/images/crewai_traces.gif'> </img>
|
||
|
||
## Troubleshooting
|
||
|
||
### Common Issues
|
||
|
||
- **No traces appearing**: Ensure your API key and repository ID are correct
|
||
- Ensure you've **`called instrument_crewai()`** **_before_** running your crew. This initializes logging hooks correctly.
|
||
- Set `debug=True` in your `instrument_crewai()` call to surface any internal errors:
|
||
|
||
```python
|
||
instrument_crewai(logger, debug=True)
|
||
```
|
||
- Configure your agents with `verbose=True` to capture detailed logs:
|
||
|
||
```python
|
||
agent = CrewAgent(..., verbose=True)
|
||
```
|
||
- Double-check that `instrument_crewai()` is called **before** creating or executing agents. This might be obvious, but it's a common oversight.
|
||
|
||
## Resources
|
||
|
||
<CardGroup cols="3">
|
||
<Card title="CrewAI Docs" icon="book" href="https://docs.crewai.com/">
|
||
Official CrewAI documentation
|
||
</Card>
|
||
<Card title="Maxim Docs" icon="book" href="https://getmaxim.ai/docs">
|
||
Official Maxim documentation
|
||
</Card>
|
||
<Card title="Maxim Github" icon="github" href="https://github.com/maximhq">
|
||
Maxim Github
|
||
</Card>
|
||
</CardGroup> |