5 points
Essentially, when your log file reaches a configured size, it should create a new one and start writing into that,
deletingarchiving the oldest
FTFY
4 points
Sure! Best practices vary to your application. I’m a dev, so I’m used to configuring stuff for local env use. In prod, archiving is definitely nice so you can track back even through heavy logging. Though, tbh, if you’re applications getting used by that many people a db logging system is probably just straight better
