Mastra Platform

Headlines · 2

1. 2d
   Mastra adds trace imports from Langfuse to pull observability history into its platform

   Mastra introduced trace imports for Mastra Platform, letting users pull existing traces from third-party observability providers into Mastra, where they appear alongside Mastra-generated traces for debugging, filtering and comparison. Langfuse is supported first, with more providers to follow; Mastra notes that observability data previously could only be exported out to third parties. Imports preserve span types such as agent_run, model_generation and tool_call, along with parent-child structure, timestamps, inputs, outputs, usage and cost, while scores, feedback, datasets, attachments and logs are omitted. The CLI requires [email protected] and @mastra/[email protected] or later and supports dry-run previews, date windows with --since/--until, and resuming interrupted imports.

   Mastra Blog · 🔥 0
2. 3d
   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 Platform experienceAsk about Mastra Platform