Mastra adds trace queries to filter agent traces by fields and nested spans
Overview
Mastra releases trace queries, which filter agent and workflow traces by time, agent or workflow ID, status, score, and feedback.
The queries also reach nested details such as failed tool calls, low scores, and thumbs-down feedback. Users can run them through the CLI, Client SDK, or HTTP endpoints.
Trace queries work on the Mastra platform and on self-hosted projects whose storage.observability uses DuckDB, PostgreSQL, or ClickHouse. Each request needs a platform access token and a project ID.
Written by AI from the articles below · updated Oct 14, 1:48 PM ET
Check the sources:
Article timeline
The articles in this story. Times are ET.
- Mastra BlogOfficialMastra adds trace queries to find slow or failed agent runs
AIMastra has released trace queries, which let users filter traces by fields such as time, agent or workflow ID, status, score, and feedback. The queries can also reach nested details like failed tool calls, low scores, and thumbs-down feedback, and can be run through the CLI, Client SDK, or HTTP endpoints. The feature works on the Mastra platform and on self-hosted projects using DuckDB, PostgreSQL, or ClickHouse storage.
Heat trend
Not enough continuous observations to show a trend yet.