braintrust

Cross-service debugging is handled by tracing interactions across Ara components like website-agent and ara-api from a single project context. You can view logs and traces together to identify where errors or bottlenecks originate across the stack.

SQL-like querying is supported to filter and drill down into Ara service traces and logs. You can write structured queries to identify specific errors, usage patterns, or performance bottlenecks across the traced components.

Structured tracing conventions and templates are provided to guide instrumenting new Ara services. These workflows ensure your code wrapping aligns with the existing Ara stack tracing standards for consistent observability.

A CLI-based toolkit is used to inspect traces, requiring you to install the tool and authenticate with a Braintrust API key. Once configured, you can run trace views directly from your terminal to begin analyzing service interactions.

Disconnected logs often occur when tracing conventions are not enforced across services. The toolkit provides structured guidelines for wrapping code, ensuring that traces propagate correctly through website-agent, ara-api, and ara.engineer components.

Performance bottleneck analysis is a core use case, allowing you to run drill-downs on service traces to pinpoint slow operations. By viewing cross-service interactions, you can isolate exactly which Ara component is causing the latency.