- Always set up logging from the start of the application, even if there is nothing to log.
- Imagine in future there is an error reported in the front-end.
- To investigate, there could be more error information in the logs.
- And even if not, to investigate further, more debug info could be added to the log temporarily, even for a specific client.
- If that requires you to set up logging infrastructure, it's much less likely to be done at all
- So it's important to have a logging system in place for that reason.
- Distinguish types of logging (see other post):
- Event - this can include debug, info, warn, error. It is logged and that's it.
- Exception - unexpected error that requires action to resolve. A human should be notified.
- Request - every request made (higher/framework level)
- ...
A piggy bank of commands, fixes, succinct reviews, some mini articles and technical opinions from a (mostly) Perl developer.
Jump to
Software logging philosophy
Ideas: