Re:Application-Level Logging Best Practices
by pojzon on Wednesday March 27, 2019 @02:35AM
(#19498582)
Its missing a part about high frequency logging.
Something like "log level checks should take only a single clock cycle"
Looks more like a dev env best practices or apps with low traffic best practices
Re:Application-Level Logging Best Practices
by YorkshireSeason on Wednesday March 27, 2019 @05:32AM
(#19499240)
Would you be able to give (link to) information about best practises for high-traffic apps?
Re:Application-Level Logging Best Practices
by pojzon on Wednesday March 27, 2019 @08:15AM
(#19500084)
I was talking from experience. Dont really follow any guidelines available online.
Re:Application-Level Logging Best Practices
by sethammons on Wednesday March 27, 2019 @09:41AM
(#19500707)
Don't forget to sanitize those API requests, else you will be like Facebook and can be logging passwords :)
log rotation
log aggregation
log errors/exceptions at the error level, and nothing else
make judicious use of trace, info, debug, etc. levels
properly namespace loggers so that the log level can be set appropriately depending on the environment and current needs
get the fundamentals right - if you are logging an exception, do you actually pass the exception to the logger? Same goes for things like failed API calls. Don't just log "API call failed". Log the entire response including status code and messages.