Add Name to Trace logs
Open
Nobody has claimed this yet.
Issue-Enhancement
Needs Triage
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the config set entry point and locate the info-level tracing around resource installation, then compare it with the more detailed trace-level output shown in the issue. Done means the resource name appears in the info-level installation logs while retaining the less crowded output requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, observability-sre
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100