#63: Logging libraries: auditing and troubleshooting your application

You can’t look at your application all the time. Instead, it should leave some sort of persistent trace. Such an audit log can be examined later on. However, it’s the responsibility of the application itself to log appropriately. But more importantly, the data it logs for later must be well-structured. Simply printing random words to a console is no longer sufficient. Read more: https://nurkiewicz.com/63 Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter