Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Hey everyone. I have had the need to log stack tracing for my errors. I wanted to know if anyone else feels the same way. I built a simple error package that will set stack trace values and has methods for outputting to map string and json. Let me know if you think this is valuable or if there is anything else you would add or change to it. https://github.com/brianvoe/uhoh
I think "github.com/pkg/errors" does this quite good actually.
We have a similar internal package where we can add per stack variables / context. We use https://github.com/maruel/panicparse to get a structured stacktrace, then append to that, and the whole json blob ships to Sentry. I think it's awesome and has almost completely eliminated any need for logging.