Vercel Launches Always-On Production Tracing
💡Debug real production requests and AI service calls without reproducing them locally.
⚡ 30-Second TL;DR
What Changed
Always-on tracing samples live Production and Preview traffic instead of only tracing the developer’s browser session.
Why It Matters
This gives teams operating AI applications on Vercel better visibility into production latency, failed requests, and outbound model or service calls. Path-scoped sampling can help control observability costs while still capturing high-value workflows.
What To Do Next
Add a narrowly scoped Production sampling rule in Vercel Settings → Tracing for one AI workflow, then inspect its trace and outbound fetch spans in Logs.
Key Points
- •Always-on tracing samples live Production and Preview traffic instead of only tracing the developer’s browser session.
- •Sampling rules support All, Production, or Preview environments and can optionally target path prefixes such as /checkout.
- •Infrastructure and outbound fetch spans are captured automatically; framework and custom spans require @vercel/otel instrumentation.
- •The beta is available on all plans at $0.50 per 1M span units, with retention ranging from 1 hour to 3 days.
Weekly AI Recap
Read this week's curated digest of top AI events →
👉Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: Vercel News ↗
This is a summary, not the original. Read the source, or get the weekly briefing.
Weekly AI briefing
One email a week. Unsubscribe anytime.