5 ms·
site seems down, but off the top of my head log rotation log aggregation log errors/exceptions at the error level, and nothing else make judicious use of tr
by mberning 8y ago
site seems down, but off the top of my head
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.
- pojzon 8y agoIts 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
- YorkshireSeason 8y agoWould you be able to give (link to) information about best practises for high-traffic apps?
- sethammons 8y agoDon't forget to sanitize those API requests, else you will be like Facebook and can be logging passwords :)