Also verified: crewai 1.15.22 with instrumentor 1.1.18. The extra no longer installs that older instrumentor. See supported frameworks for how verification works.
In code
Calltracing.init(), attach the framework instrumentor to the provider it returns, and wrap the work in tracing.turn() and tracing.agent().
CrewAI calls its model through the OpenAI SDK, which the CrewAI instrumentor doesn’t trace. The
[crewai] extra therefore also installs the OpenAI producer, and the install line pins the tested openai. CrewAI 1.15 needs Python 3.10 to 3.13 and doesn’t support 3.14. Set CREWAI_DISABLE_TELEMETRY=true to stop CrewAI’s own usage telemetry.1
Install
terminal
2
Add the code
app.py
3
Run
terminal
BOTGAUGE_API_KEY, OPENAI_MODEL, OPENAI_BASE_URL, OPENAI_API_KEY.Zero-code
Leave your app unchanged and start it withbotgauge instrument. The sample still wraps the work in tracing.turn() and tracing.agent() so spans carry session and agent ids.
CrewAI calls its model through the OpenAI SDK, which the CrewAI instrumentor doesn’t trace. The
[crewai] extra therefore also installs the OpenAI producer, and the install line pins the tested openai. CrewAI 1.15 needs Python 3.10 to 3.13 and doesn’t support 3.14. Set CREWAI_DISABLE_TELEMETRY=true to stop CrewAI’s own usage telemetry.1
Install
terminal
2
Add the code
app.py
3
Run
terminal
BOTGAUGE_API_KEY, OPENAI_MODEL, OPENAI_BASE_URL, OPENAI_API_KEY.View CrewAI spans live
Watch your CrewAI runs and underlying LLM calls appear in BotGauge.
.png?fit=max&auto=format&n=rExdh2xAS2_ywWU5&q=85&s=2336659947d2543be68f95bf2d539b85)