Currently, if the logger handles an internal error we don't know where the issue occurred. If we add a call stack trace to those logs it will be much easier for a developer to debug the issue.

Example internal error:

E0616 19:09:18.042650       1 logger.go:121] [opid=2ybQjbNaqBUy3sOZ1JjtNMu2D2P] OCM-SB-9: Unable to find Service with fullname='OSDv4/rosa-hcp-fleet-wide/ROSAHCPNodepoolUpgradeSuccess': context canceled