microsoft / microsoft/PSRule

[FEATURE] Diagnostic logging core engine

Open
#2,894 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

.NET feature: diagnostics
Dominant language
C#
Stars
474
Forks
65
Avg merge
22h 25m
Merged PRs (30d)
26

Description

Your suggestion

These are enhancements to the logging experience for debugging across PSRule core engine and any infrastructure and options required to support extensibility and rule diagnostics.

Alternatives

n/a

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names the PSRule core engine and the infrastructure and options needed for extensible diagnostic logging, but it does not identify files, tests, or an entry point. Start by mapping the core engine's current logging behavior and determine the required extensibility scope. Done should mean the diagnostic logging enhancements and supporting infrastructure are defined and implemented, with coverage for the intended diagnostics.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, powershell
Domain
observability, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.