Understand this story
On October 28, 2026, Mastra launched Span Queries, which can filter and group individual spans across all traces by conditions such as time range, type, name, status, error, and duration, to help locate common failures in coding agents. This feature is available in Mastra platform, Studio, CLI, Client SDK, and observability endpoints. Each query can combine up to 100 conditions, return up to 1,000 spans per page, group by up to 2 dimensions, and cover a time range of up to 365 days; the CLI requires mastra@1.36.0 or later, and the SDK requires @mastra/client-js@1.57.0 or later. Self-hosted projects can also use it when storage.observability uses DuckDB, PostgreSQL, or ClickHouse. There are currently no further developments.
AI-generated from public reports
Latest development · Report
Mastra Launches Span Queries: Filter and Group by Span to Pinpoint Common Coding Agent FailuresDevelopments
1 confirmed developments
- Source:Mastra Blog
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Oct 28
Mastra BlogFirst-party
Mastra Launches Span Queries: Filter and Group by Span to Pinpoint Common Coding Agent Failures
Mastra has launched Span Queries, which can filter and group individual spans across all traces by conditions such as time range, type, name, status, error, and duration; it is available in Mastra platform, Studio, CLI, Client SDK, and observability endpoints. Each query can combine up to 100 conditions, return up to 1000 spans per page, group by up to 2 dimensions, and cover a time range of up to 365 days; the CLI requires mastra@1.36.0 or later, and the SDK requires @mastra/client-js@1.57.0 or later. Self-hosted projects can also use it when storage.observability uses DuckDB, PostgreSQL, or ClickHouse.