Skip to main content

📊 Beak AI Observability – Release Notes

Changes and updates for trace visualization, evaluations, and performance tracking.

Version 6.0.0​

A new tenant's trace tables are created, and partitioned by time​

Creating a tenant now sets Observability up for it. Its tables used to be copied from an existing tenant, along with a separate engineering step that made the trace, span, evaluation and alert tables time-partitioned — a tenant provisioned any other way got ordinary tables that looked correct and did not stay fast as they filled.

  • Traces, spans, evaluation results and alert events are partitioned on creation, at the same intervals production uses.
  • Nothing to configure. Observability reports itself ready as soon as its schema exists: traces arrive from the other products as the tenant uses them, and alert and evaluation rules stay opt-in.

On by default for newly created tenants. Existing tenants are untouched — a table that is already partitioned is left exactly as it is.

Version 1.0.0​

  • Initial trace and evaluation viewer.