Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

Systematic logging support #83

Closed
chungers opened this issue Jun 27, 2016 · 4 comments
Closed

Systematic logging support #83

chungers opened this issue Jun 27, 2016 · 4 comments
Labels

Comments

@chungers
Copy link
Contributor

Right now logging is pretty ad-hoc. Other than using logrus here and there, there is no pattern or systematic support for provisioner developers. docker-machine exposes logger for driver developers to use and libmachete should as well.

@wfarner
Copy link
Contributor

wfarner commented Jun 27, 2016

Clarifying - the goal is a modest one (rather than a logging API facade); to add a GetLogger() function somewhere that makes it obvious which logger to use.

@linsun
Copy link
Contributor

linsun commented Nov 1, 2016

We really need to enhance the logging support. First of all, all logging should have timestamp. 2nd, the current code has little or no log, it is really hard to debug things when stuff goes wrong.

@wfarner
Copy link
Contributor

wfarner commented Nov 1, 2016

@linsun completely agreed that logging is too sparse right now. This issue relates to a logging framework for use in plugins, so i've filed #269 to track improvements to the thoroughness of logging.

@chungers
Copy link
Contributor Author

#440 implements this

chungers pushed a commit to chungers/infrakit that referenced this issue Sep 30, 2017
…ploy-documentation

remove non-required instructions and improve docs
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants