-
Notifications
You must be signed in to change notification settings - Fork 341
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
Better logging #22
Comments
Lines 3 to 4 in c61fe70
🤯
|
@0x2b3bfa0 I dont fully follow you 😁 |
If you are wondering what is does is prevent other libraries to output in std with console.log. Take into account that console.log is used even is you dont want to |
Thanks! I was wondering (admittedly, with a bit of humor) if we could avoid monkey-patching once we improve logging. The current approach is equally useful and puzzling if you overlook those lines. |
Yeah, JS and its weirdness. Mostly all the logging libs do this internally |
@DavidGOrtega, feel free to create a new issue starting from the following template and elaborating on each idea, if opportune:
|
This could be maintained as an epic? |
I plan to create a new follow-up epic from #703 and we can include all the relevant issues there. |
Use a proper logging library
console.log
into proper logger calls@0x2b3bfa0 moved the rest of items to a separate issue, as @casperdcl suggested in the past weekly meeting.
Click to see the original text...
nice to have
(put in separate issue)
Edit:
Coming back to this we should now, with the 0.3.0 release, attack this.
The proposal would be use winston and a configurable file. We can also collect runner heartbeat using openmetrics format
The text was updated successfully, but these errors were encountered: