-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Adds npmlog as default logger #1209
Conversation
Current coverage is
|
Shouldn't these be going into the LoggerAdapter? |
The logger adapter is not final and not used. It does 2 things now. 1 configure Winston, 2. Provide an API for the logs endpoint. For now, we don't use Winston at all. And if we were to use it, we'd need to decide what logs go there. console.log don't go to Winston, nor we expose the logger anywhere else. |
We'd like to expose the logger endpoint so you can see your logs on the dashboard. Obviously it's not there yet, but this seems like a step in a different direction. |
Yeah, I know... I'm adding winston instead now, but I'm not sure this is the right direction either... |
With the logger adapter you should be able to just plug in any logger. Having a default seems fine, as long it just works out of the box. |
Yeah but that's not the issue, we have server logs for debug, verbose purposes, request traces, cloud code logs etc... |
It probably should be. I think our logging infra is scattered and awful right now and I think we should be making it more unified and useful rather than adding more log systems. |
Yeah that's why I'm moving back to winston. |
No description provided.