PowerShell
Need to support directing all messages to logs
Summary of the new feature / enhancement
Support ETW and syslog
Proposed technical implementation details (optional)
No response
For all cases where dsc.exe writes to stderr/stdout, we should abstract to calling an internal logging function that can also output to console for interactive use
Big endorsement for otel - used it in my last role and it was incredibly good for bubbling up information. It's not much extra work to add a flag that makes a command emit the otel logging to stderr for debugging either.
Consider providing an option to write detail dsc operational logs to file
- This can include various component logs involved in invocation of the resources.
- It will help identify resource issue vs dsc (platform) issue.
- Provide retention policy for logs and log rotations.
- One possible open source xplat logging library: - https://github.com/gabime/spdlog
We should use https://docs.rs/tracing/latest/tracing/ which can integrate with OpenTelemetry
Expose --loglevel [warning|info|debug] (terminating errors should always be logged. Then also separate parameter(s) to log to console (default), system (etw/syslog/oslog presumably via opentelemetry), file.
Try looking at https://github.com/open-telemetry/opentelemetry-rust to see if it abstracts the different logging files/formats