To collect trace logging while also providing a Fiddler trace from the client side, you can use the TroubleShootingScript (TSS) toolset in PowerShell. Here’s a basic script to enable trace logging:
# Enable a scenario trace
.\TSS.ps1 -Scenario <ScenarioName>
# Enable component traces
.\TSS.ps1 <-ComponentName> <-ComponentName> ...
# Start traces with no-wait mode
.\TSS.ps1 -StartNoWait -Scenario <ScenarioName>
# Stop the trace when needed
.\TSS.ps1 -Stop
Make sure to replace <ScenarioName> and <ComponentName> with the appropriate names for your specific scenario. You can list supported scenarios and components using the following cmdlets:
.\TSS.ps1 -ListSupportedScenarioTrace
.\TSS.ps1 -ListSupportedTrace
Additionally, ensure Fiddler is set up to capture the necessary traffic by enabling HTTPS decryption and capturing traffic as outlined in the Fiddler documentation.
References: