PowerShell / PowerShell/PSScriptAnalyzer
Optional logging metrics for rule applications
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Tobias has suggestions around adding useful metrics for rule applications.
Context:
"It would be extremely helpful to have metrics about how often a rule was applied, how often it was violated, and how long evaluation took.
It could be controlled via opt-in so logging is off until you turn it on.
This way, we all could identify the rules violated most often, and initiate educational initiatives, plus find out more about rule quality and relevance.
The best way to consume this info would be through event logs. This would not replace my original suggestion of having a “-Diagnostic” switch. The –Diagnostics switch would apply to the current scenario only and return metrics immediately.
"
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
The issue does not name files, tests, or entry points. Begin by locating where rules are applied and evaluated, then determine how opt-in event logging and the proposed diagnostic switch should expose application counts, violations, and evaluation time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- devtools, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100