Empowering OpenTelemetry: How we made Next.js app work with a self-hosted collector
summary
Shows how a Next.js app on Vercel serverless functions sends traces, metrics and logs to a self‑hosted OpenTelemetry Collector (deployed via Kubernetes Helm) because Vercel’s built‑in integration only ships traces. Finds exporters stop because Vercel freezes the Node runtime right after response, implements a wrapper that overrides response.end to flush spans/metrics/logs before return, and reports the approach works for serverless functions but not for edge or client code.
AI-written summary · about
related talks
01h 01mLearnings from One Year in Production with Next.js on Vercel
49mAdding OpenTelemetry to Production Apps Lessons Learned
25mOpenTelemetry for Platform Engineers: Paving the Road To Self-Service Observability
22mBridging the OpenTelemetry Adoption Gap in Cloud-Native Applications
35mOpenTelemetry for Busy People
28mImplementing Observability in Kubernetes
27mEnd-to-end visibility in the cloud w/OpenTelemetry
34mDistributed Tracing Integration with OpenTelemetry and Knative