Mastra Client SDK

Headlines · 2

1. 2d
   Mastra launches Trace Queries for filtering and debugging agent traces

   Mastra introduced Trace Queries, letting users filter and find traces in the Mastra platform and local Studio by trace fields such as time, primitive name, agent/workflow ID, status, score and feedback, and build the same queries via the CLI, the Mastra Client SDK or HTTP observability endpoints. The feature can reach low-level information nested inside a trace — a failed tool call, a low score or thumbs-down feedback — so a coding agent can query for errored or failed traces and slow model calls and then fix them. Each query covers a time range of up to 31 days and can combine up to 100 conditions, with up to 8 filters on trace internals (spans, scores, feedback) and operators including and/or/not, eq, gt, exists and matches; self-hosted projects need DuckDB, PostgreSQL or ClickHouse for observability storage. The CLI requires [email protected] or later and the client SDK requires @mastra/[email protected] or later.

   Mastra Blog · 🔥 0
2. 4d
   Mastra launches Metrics API for token usage, cost and latency

   Mastra introduced a Metrics API that lets developers query token usage, model cost, latency and error rates for production projects through the Mastra Client SDK, Mastra CLI or observability endpoints. The API supports totals, breakdowns, time series and percentile queries, combinable with time ranges and status filters, for custom reports, dashboards, downstream data pushes or alerts when model costs or error rates rise. According to the Mastra blog, queries require a platform access token and project ID plus the region-specific observability base URL (US and EU), with @mastra/client-js 1.9.0+ and mastra CLI 1.9.2+; Mastra also says the API can be paired with code mode so agents construct their own queries.

   Mastra Blog · 🔥 0

Experience and discussion from the community

Share my Mastra Client SDK experienceAsk about Mastra Client SDK