Mastra adds span queries: traces no longer come back whole, so failing tool calls surface directly
Mastra has introduced span queries, moving observability queries from the whole trace down to individual spans inside it. Trace queries could already filter on deep details such as a failed tool call, but they still returned the entire trace, making the problematic call hard to spot. Span queries search within each trace and return only matching spans, and matching spans can be grouped or aggregated into counts, error rates and latency to show which tool is failing or slow.