Last week we had a deploy on Suga that was taking longer than usual. It was hard to reproduce, so the only obvious thing to do was try and trace it end to end. We immediately ran into roadblocks because the trace only covered the first 140 milliseconds. For context: the bulk of our deployment code runs in a background worker and is triggered via a queue, and the worker's trace had no connection ba
Three days debugging a missing trace
Rak·Dev.to··1 min read
D
Continue reading on Dev.to
This article was sourced from Dev.to's RSS feed. Visit the original for the complete story.