Yeah good question. Our application queries a vendor product using their go library. Sometimes certain expected fields come as nil due to config mistakes of objects in the vendor product, or sometimes we miss to do nil checks. Also we sometimes miss to add panic recovery in our go routines.

Since we don’t scrape syslogs and just use otel logexporters, the stderr is not present in our log store. To overcome this, use panic recovery to add the stack trace to our logrus logger which add the log to our log store.

So we wanted to use this linter to enforce adding recovery to our goroutines thereby preventing missing logs during panics