Please enable JavaScript.
Coggle requires JavaScript to display documents.
Logging Standards (What should be logged (Work Smarter, Not Harder (User…
Logging Standards
What should be logged
Log all the things. Log as much as we possibly can, to always have relevant, contextual logs that don’t add overhead.
Work smarter, not harder. Consolidate and aggregate all of our logging to a central location, available to all devs, and easy to distil. Also, to find new ways for our logging and exception data to help us proactively improve our product.
-
-
Logs easy to read, easy to parse
-
Logging Levels
-
Trace/Debug
Most detailed logging. Should not be recording this level in production environments unless necessary for troubleshooting a problem.
Warning
Incorrect behaviour, but the application can continue.Logging of non critical issues, that should be fixed. Example a missing configuration value, that now uses default.
Errors
Exceptions that occurred, should have exception information, stack trace, input values, ...
-
-
Logging Scope
Bad
-
fragile information (security of personal data, passwords),
-
-
Good
-
system events (startup, closing, changing date),
-
authentication success and fail,
-
-