CrewAI
The BlueRock runtime provides native, out-of-the-box telemetry tracing for multi-agent orchestrations built using the CrewAI framework. By embedding the bluerock Sensor directly into the execution space, BlueRock automatically hooks into CrewAI's lifecycle hooks without requiring codebase alterations or manual analytics callbacks.
Core Architecture & Telemetry Pipeline

Environment Setup
Provision the Isolated Project Environment Initialize the local configuration layout with
uvto ensure strict, repeatable dependency management across testing environments:
Inject and Register BluePython Sensors Deploy the custom BlueRock telemetry sensor library directly within the activated workspace context:
Agent Execution Block
Create the localized controller file as help_agent.py to initiate multi-agent execution. Ensure appropriate authorization environment variables (OPENAI_API_KEY) are bound to the parent terminal session:
Captured OpenTelemetry (OTEL) Lifecycle Events
During validation phases, the active bluepython sensor writes structured payloads tracking the progression of multi-agent orchestration states.
Phase 1: Crew Initialization (crew_kickoff_started)
Triggers at the entry boundary of the collective execution loop, registering involved roles, input properties, task items, and processing schemas.
Phase 2: Task Provisioning (task_started)
Logs properties when an item is dispatched to a specific worker agent, recording intent requirements, expected resolution criteria, and assigned tool layers.
Phase 3: Runtime Execution Profile (agent_execution)
Captures structural metadata associated with individual execution states, auditing behavioral guardrails such as target model variants, delegation permission rules, and backstories.
Phase 4: Execution Resolution (agent_execution_completed)
Marks task completion steps, registering structural text output answers, verification states, and usage parameters.
Last updated