Currently, we are using the in built error handling of go. The issue with this is that, by default, the errors do not come with stack traces which makes it harder to debug and triage any issues that might arise.

For this reason, we should move to pkg/errors that allows you to attach a stack trace at whatever point an error is introduced.

Fixing this issue should not be the final time that we revisit error handling. Down the line we should come up with a set of standardized errors and a set of guidelines on how to approach error handling, where to add additional context, where to attach the error stack, and so on.