In initial design, logger is also a registry, after #78 logger and logger registry got split up, however there is no global registry #97, so most of the time it's not ready for use out of the box, and the struct logger is actually not that useful when the filter util (both runtime #23 and post processing #89) is not used, also the identity is causing trouble but never get used #108
[ ] rename package to dlog, this solve the rename for package logger so no import is needed
only go.ice & ayi needs to be changed, since all the other projects are no longer active ...
[ ] simplify registry creation logic
not sure if the old logutil per project is a good idea, for project maybe, for library it is almost same as having a global registry except more verbose
[ ] make the registry useful
allow config using flag (could provide a cobra binding, or snippet for copy and paste)
allow config using http endpoint, provide a handler like pprof
[ ] clean up handler code and example
[ ] write a clean doc for design, the log doc is good, but still need an in place update doc for the latest design (otherwise need to replay the logs to get a state of current design ....)
In initial design, logger is also a registry, after #78 logger and logger registry got split up, however there is no global registry #97, so most of the time it's not ready for use out of the box, and the struct logger is actually not that useful when the filter util (both runtime #23 and post processing #89) is not used, also the identity is causing trouble but never get used #108
dlog, this solve the rename for package logger so no import is neededlogutilper project is a good idea, for project maybe, for library it is almost same as having a global registry except more verbose