The Go Error You See Is Never the Real Error
We wrapped errors, logged them, and monitored them. The one that mattered at 3AM was three layers below what our dashboards showed. Continue reading on Level Up Coding »
Read the full articleYou might also wanna read
Go's lack of stack traces in errors reduces log usefulness for debugging
Logs are the primary way to understand what your system is doing, and error logs most of all. But your logs can only surface what your error
robinsiep.com·1mo ago
Understanding a Subtle Bug in Go's errgroup and the Importance of Testing
Table of contents
gaultier.github.io·11mo ago
Elevated errors across many models
Jul 4 , 00:20 UTC Resolved - This incident has been resolved. Jul 4 , 00:19 UTC Monitoring - A fix has been implemented and we are monitorin
Elevated errors across many models
Jun 22 , 19:45 UTC Resolved - This incident has been resolved. Jun 22 , 19:20 UTC Monitoring - A fix has been implemented and we are monitor
Elevated errors on multiple models
Jul 8 , 18:28 UTC Identified - We have identified an issue causing elevated errors on requests to some models, and our team is working to re
Elevated errors for some models
Jul 7 , 20:28 UTC Identified - We have seen success rates return to normal, but we are continuing to work to fully resolve this issue and en
Comments
Sign in to join the conversation.
No comments yet. Be the first.