How are people debugging prod issues on Vercel?

Hi,

I’m a student working on a summer project.

I’m trying to understand how people actually debug production issues, especially after a bad deploy hits clients and you’re on the clock to get things working fast.

Should I start with Vercel logs, GitHub commits, traces?? Also, how can I decide when to roll back vs. hotfix vs. keep digging?

I feel like shipping has gotten way faster, but figuring out what broke is still pretty manual. Any ideas?

1 Like

I usually start with browser dev tools and Vercel runtime logs. From there, it depends on what’s going wrong.

Instant rollback can help when you want to get Production working again but you’re not able to find and solve the production issue quickly

1 Like