You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment we make use of the logger as an access log, refraining from logging errors outside of those that trigger HTTP 500s. This isn't particularly useful as a debugging aid as it prevents us from logging the context that'd be useful to help diagnose issues.
Should we consider making the existing log messages part of our interface and testing against them, or should we refocus logging around diagnostics and error conditions?
The text was updated successfully, but these errors were encountered:
At the moment we make use of the logger as an access log, refraining from logging errors outside of those that trigger HTTP 500s. This isn't particularly useful as a debugging aid as it prevents us from logging the context that'd be useful to help diagnose issues.
Should we consider making the existing log messages part of our interface and testing against them, or should we refocus logging around diagnostics and error conditions?
The text was updated successfully, but these errors were encountered: