Skip to content
This repository has been archived by the owner on Nov 15, 2022. It is now read-only.

Use proper logger instead console.log #111

Open
Bigomby opened this issue Apr 14, 2020 · 1 comment
Open

Use proper logger instead console.log #111

Bigomby opened this issue Apr 14, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@Bigomby
Copy link
Member

Bigomby commented Apr 14, 2020

Currently the application is using console.log for logging. We should avoid using it on production, instead a proper logger should be used.

I propose pino, which has good performance and outputs useful info for production environments and pretty logs in development environments.

@Bigomby Bigomby added the enhancement New feature or request label Apr 14, 2020
@Bigomby Bigomby mentioned this issue Apr 14, 2020
4 tasks
@mariopino
Copy link
Contributor

Hey @Bigomby, is something blocking this? I think we just need to:

  • Research how to integrate with docker logs and include in documentation. Note that main goal for logging at this stage is to help debugging and I think a more human logging would help. Reference: pretty logs with docker pinojs/pino#178
  • Replace all console.log by pino logger calls in all places.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants