xDscDiagnostics
xDscDiagnostics copied to clipboard
dsccommunity
This module contains cmdlets for analyzing DSC event logs.
#### Details of the scenario you tried and the problem that is occurring When getting data using Get-xDscOperation the output isn't continous. #### Steps to reproduce the problem ~~~~ Get-xDscOperation...
I'm on a fresh Windows Server 2019 v1809 trying to play around with xDscDiagnostics (stable). Get-xDscDiagnostics work, but trace doesn't. Also I get an exception instead of a nice error...
See lines 343ff --- This change is [](https://reviewable.io/reviews/powershell/xdscdiagnostics/42)
We are exporting the data from event logs to the disk.
A cmdlet with 'New verb should not be aliases with a verb 'Get' ... these noun represent 2 different actions.
Calls to Trace-xDSCOperation fail as assignment of EventType property to TraceOutput Object fails as EventType is $null. # Repro on Windows 10.0.17763 (get-winevent -LogName 'Microsoft-Windows-Dsc/Operational' -MaxEvents 5) | where-object {$_.ContainerLog.endsWith("operational")}...
additionally, enable automatically collecting if it is present
- We are logging some important logs in to the debug channel and the tool does not currently collect debug channel logs. * It will be helpful to trouble shoot...
In order to have more complete data collection we also need these logs: Microsoft-Windows-DSC/Analytic Microsoft-Windows-DSC/Debug
Certificate misuse for password encryption and decryption seems to be a common scenario. update the xDScDiagnostics to collect information related to certificates. The following are some examples. - Certificate ID...
Metadata
Owner
Metadata
This module contains cmdlets for analyzing DSC event logs.