Skip to content
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

Improve logging #140

Open
neophob opened this issue Nov 9, 2019 · 2 comments
Open

Improve logging #140

neophob opened this issue Nov 9, 2019 · 2 comments
Labels
boring Some VP internals that need to be ported (or not) enhancement New feature or request

Comments

@neophob
Copy link
Contributor

neophob commented Nov 9, 2019

In my PR @freezy add a comment:

I usually try to prefix logs with where it occurs: [Myclass.myMethod]: My message

Make sense - why not improve the whole logger, some ideas:

  • create a instance with its class name as prefix
  • use debug - dynamic enable debug logging for certain classes might help
  • future improvements, when public - send error logs to log aggregator to get realtime feedback
@neophob
Copy link
Contributor Author

neophob commented Nov 9, 2019

Potentail cloud log aggregator:

@neophob
Copy link
Contributor Author

neophob commented Nov 10, 2019

Next pragmatic step:

  • use debug - enables dynamic change of log level or depending on package (browser & node)
  • will too a PoC
@freezy freezy added boring Some VP internals that need to be ported (or not) enhancement New feature or request labels Nov 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
boring Some VP internals that need to be ported (or not) enhancement New feature or request
2 participants