-
-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Codebase Should support usage of a daily rotating file logging system #638
Comments
Hi , Can I work on this issue? |
if @alexanmtz approves. wrote some stuff on it lately |
that's great @Adekoreday, very good article. So you're interested to work on this? Or you want to share your reference so other contributors can learn from your article? |
Sharing my reference to make the task easier for @navneet79 |
@navneet79 are you still interested or should I take up the task? |
@alexanmtz will like to go ahead and implement this |
hey @Adekoreday you want to continue to work on this? Do you want to be assigned? |
i'll continue work on this was waiting on your approval |
Great @Adekoreday , you're now assigned 👍 |
Description
Why
Logging of details and error on the console makes it difficult to have a detailed history of errors and user interactions with the application on production over a long period of time.
Level
Beginner
Current behavior
On start of the application details of interactions are logged via the console, this makes it difficult to know the following
Expected behavior
A daily rotating file logging system should log information on files, console, and optionally a configuration to enable logging on file or console or both depending on the environment.
After 24hours each log file should be zipped to keep our application size in check.
Screenshot attached
How to reproduce the user scenario
Tips
leverage of node.js logging libraries
The text was updated successfully, but these errors were encountered: