Braintrust puts application logs in public preview alongside agent traces

Braintrust has put application logs in public preview, combining them with agent traces in a shared view. The release extends the platform from agent observability to logs from services, including those that run independently of agents. Engineers can inspect logged errors and retries alongside agent actions and responses, without switching systems. The preview is available to Braintrust SaaS and BYOC customers, and to self-hosted customers running data plane 2.14 or later.

In the log view, users can search records, choose time ranges, filter by severity and inspect application-recorded metadata. Message templates can group recurring events while retaining the varying values attached to each event, such as different payment identifiers. The Python SDK captures templates and their values automatically when developers use named parameters. Braintrust also supports SQL queries over logs, including questions about which errors appeared most often during the previous day.

When an application log is connected to a trace, users can view it alongside the agent steps associated with it. For example, after a tool request times out, a developer can examine the error and determine whether the agent retried, switched tools or returned an answer. For AI builders, this joined context can help investigate failures across both the application and the agent rather than treating them as separate systems. Braintrust says its trace query tools can also filter log messages and inspect specific fields.

Teams can start by sending logs from a single service, with or without an active trace. They can use the Python SDK or send logs from another language through an OpenTelemetry exporter or collector. The Python setup requires SDK version 0.42.0 or later. Self-hosted customers need data plane 2.14 to access the preview, while SaaS and BYOC customers are included in its availability. To connect logs with a particular operation, developers must include that operation’s trace context when sending the logs.