Braintrust brings application logs into its agent-tracing view

Braintrust announced a public preview of application logs in a post dated October 8, 2026, extending its agent-observability tools to ordinary service logs. The company says developers can inspect those records and agent traces in one view rather than switch between systems.

The post illustrates the connection with a timed-out tool request: a developer can examine the error alongside the agent’s next steps, whether it retried, chose another tool or returned an answer. To connect a log to a specific operation, senders must include that operation’s trace context. Logs can also be sent without an active trace.

The scope extends beyond services attached to an agent. Braintrust says teams can send logs from independently running services, including databases and background workers, and use its Patterns tool to look for recurring problems. Patterns or a custom Loop automation can review logs and traces on a schedule.

For individual investigations, the company describes full-text search, time-range selection, severity filters and access to the metadata recorded by an application. SQL queries can surface the most frequent errors. Message templates provide another way to group repeated events without losing the values that distinguish each occurrence; Braintrust says its Python SDK preserves those templates and values automatically when developers use named parameters.

According to the announcement, the preview covers all Braintrust SaaS and BYOC customers, plus self-hosted deployments starting with data plane 2.14. Ingestion is available through the Python SDK—version 0.42.0 or later—or through an exporter or collector supporting OpenTelemetry’s OTLP protocol.