rangan-msft
commented
8 years ago Troubleshooting Intent
It depends on the type of logging that is desired. For example, I have used Serilog (https://serilog.net/) for structured logging and it has several sinks (https://github.com/serilog/serilog/wiki/Provided-Sinks), you can add one or use an existing one (I used elasticsearch sink). It doesn't mean the data is going to look pretty (primary intent is troubleshooting issues for which logs are sufficient), these are logs so we will have to do some additional work to make it look better if we wish to share the data.
We could take a dependency on it and by default write to console and leave the option of configuring a sink to the consumer of CBT.
Metrics tracking intent
We could use Serilog here as well or look at other options.
At some point we'll need a telemetry story for tracking usage. This will be good for general reporting and for communicating updates to modules/packages.
I'd like to try and leverage some existing open-source system that is used widely.
For now we could make people Watch the repos but we need a better long term solution.