https://imawilson.com/posts/Recent content in Writing on Greg WilsonHugoen-US&copy; 2026 Greg WilsonFri, 10 Jul 2026 00:00:00 +0000https://imawilson.com/posts/mastra-agent-grafana-dashboard/Fri, 10 Jul 2026 00:00:00 +0000https://imawilson.com/posts/mastra-agent-grafana-dashboard/<p>A single Grafana dashboard is enough to watch a Mastra agent during an incident: five golden-signal numbers, a p95 latency, and the throughput and spend underneath. Because the exporter emits Prometheus histogram buckets, the p95 is a true windowed percentile, and every spike is tagged with its <code>trace_id</code> as an exemplar. This post builds that board, panel by panel, and ships the <a href="https://imawilson.com/posts/mastra-agent-grafana-dashboard/overview-dashboard.json" download>provisioned JSON</a> so you can drop it into your own Grafana.</p>https://imawilson.com/posts/export-mastra-agent-metrics-to-prometheus/Fri, 03 Jul 2026 00:00:00 +0000https://imawilson.com/posts/export-mastra-agent-metrics-to-prometheus/<p>Mastra derives per-agent metrics (latency, tokens, cost) from its traces, and shows them well in Studio. When you want those metrics in Prometheus so your production monitoring and alerting can use them, you need a scrape endpoint that Mastra doesn&rsquo;t ship. You can add one without running an analytics database. Mastra puts every derived metric onto an observability event bus, so a small exporter can listen, feed <code>prom-client</code>, and serve <code>/metrics</code> from memory, with no analytics database (DuckDB or ClickHouse) to run. Here is how I wired it up, and the <a href="https://github.com/charlesgwilson/mastra-prometheus-exporter" target="_blank" rel="nofollow noopener noreferrer">open-source exporter</a> that does it.</p>