DSC
DSC copied to clipboard
PowerShell
Add Name to Trace logs
Summary of the new feature / enhancement
When tracing-level=info, can we add the name of the resource we are installing? Makes it easier to troubleshoot which section in yaml I need to modify
./dsc --trace-level info config set -f dev-tools.dsc.yaml
2025-03-15T01:24:14.006751Z INFO Trace-level is Info
2025-03-15T01:24:14.007476Z INFO Discovering resources using filter: *
2025-03-15T01:24:14.023109Z INFO No parameters defined in configuration and no parameters input
2025-03-15T01:24:14.026180Z INFO Getting current state for set by invoking get on 'DSC.PackageManagement/Brew' using 'brew.dsc.resource.sh'
2025-03-15T01:24:15.117980Z INFO Invoking set 'DSC.PackageManagement/Brew' using 'brew.dsc.resource.sh'
2025-03-15T01:24:16.542062Z INFO Invoking get 'DSC.PackageManagement/Brew' using 'brew.dsc.resource.sh'
2025-03-15T01:24:17.583851Z INFO Getting current state for set by invoking get on 'DSC.PackageManagement/Brew' using 'brew.dsc.resource.sh'
2025-03-15T01:24:18.609763Z INFO Invoking set 'DSC.PackageManagement/Brew' using 'brew.dsc.resource.sh'
2025-03-15T01:24:20.060043Z INFO Invoking get 'DSC.PackageManagement/Brew' using 'brew.dsc.resource.sh'
2025-03-15T01:24:21.116054Z INFO Getting current state for set by invoking get on 'DSC.PackageManagement/Brew' using 'brew.dsc.resource.sh'
2025-03-15T01:24:22.252279Z INFO Invoking set 'DSC.PackageManagement/Brew' using 'brew.dsc.resource.sh'
2025-03-15T01:24:33.707525Z INFO Invoking get 'DSC.PackageManagement/Brew' using 'brew.dsc.resource.sh'
Proposed technical implementation details (optional)
You can see it in tracing-level=trace but it's a bit crowded
To be sure I understand, is the request here to have the DSC.PackageManagement/Brew resource report informational logs, or for the DSC logging itself to tag the resource instance name in the info logs, or both, or something else?
Either the actual package names homebrew is installing or the name of the task that is leveraging homebrew works.