Vercel Sandbox now supports memory observability
Vercel Sandbox adds memory observability—P75, P95, and CLI metrics now available to catch runaway functions before they fail.
Why it matters
Developers building on Vercel Sandbox can now measure and alert on memory usage patterns across sandboxes, closing a gap in production observability for serverless workloads. Actionable for teams running compute-intensive tasks and needing to optimize cold-start or resource ceiling risk.
The key facts
11 to knowMemory Usage card reports average, P75, and P95 memory across sandboxes
Available in dashboard, CLI (vercel metrics), and Observability query builder
memoryUsedBytes measure on sandbox usage event enables custom queries and alerts
Y-axis auto-scales to sandbox memory limit; 85% threshold reference line added
CLI returns metric, reporting period, measurement interval, project, min/max/avg graph
Feature available across sandbox overview, project, and team-level pages
Memory usage reported as average, P75, P95 across sandboxes
Available in dashboard, CLI (vercel metrics command), and Observability query builder
Memory ceiling visualization with 85% reference line on sandbox detail page
memoryUsedBytes measure added to sandbox usage event for custom queries and alerts
CLI access via vercel metrics under vercel.sandbox.memory_used_bytes; --all flag for team-level aggregate
Go to the source
Vercel Blogvercel.com
Publisher excerpt: now includes memory usage data.Vercel Sandbox observability You can access sandbox memory usage data in the dashboard and through the CLI via the command. vercel metrics The Memory Usage card reports average, P75, and P95 memory across your sandboxes, alongside the existing CPU usage and data…