Menu

1 / 2

Why your Sentry events never reach your serverless functions

DEV Community·Michel Faure·6 months ago
#iCHWgxlf
#sentry#vercel#nextjs#flush#cron
Reading 0:00
15s threshold

The morning Sentry lied to me, in the wrong direction

A Tuesday morning in mid-April, I open the cron digest of Rembrandt , the ERP I've been coding alone for L'Atelier Palissy. The day before, I had finally wrapped four critical crons with Sentry.withMonitor to get readable SLOs, and I was waiting for that first digest like a Sunday morning of league results. The board is red. 41 timeouts on sync-formidable over five hours, 9 on check-replies , 1 on sync-pennylane , and a 5xx API SLO firing for good measure. I sit down.

Niran, the twenty-year-old intern who spends his Saturdays at the dojo and his weeks in a dark hoodie, is already at his desk, soda can next to the laptop. He glances at my screen, glances at Supabase Studio , and drops without looking up: "Yesterday's leads are in the database." They are. Inserts into contacts happened, the lead-pipeline tasks ran, the Slack notifications went out. The cron did its job.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.