Details
-
Task
-
Resolution: Fixed
-
Major
-
None
-
None
-
5
Description
At present we propagate errors to the top of the reconciler then call logr.Error(), which is good because it gives us a back trace, however bad because it's the same back trace every time. If we used errors.Errorf it would collect a stack trace at the point of origin.
Slight caveat is that extracting said trace and marshaling it into a zapr structured log is not totally clean, but doable...