Purpose
The purpose of this article is to provide clear ordered steps for users of PowerShell Universal and to submit them to Ironman Software (typically for a support case).
Background
Having logs from PowerShell Universal is typically needed to assist with troubleshooting issues. Providing a quality bug report can help to speed up the time to resolution.
Version 4.x Procedure
1. Recreate the issue (if applicable) and note the time ⌚
2. From the PowerShell Universal console, navigate to 'Platform', 'Logging'.
3. Click 'Download System Logs' to download a .zip file containing the logs.
4. Attach the .zip to your case (ticket) once you raise one using the 'Contact Us' dialog of the Ironman Software home page.
5. Please include a summary that explains the issue that is occurring along with the timestamp of approximately when the issue occurred.
Log verbosity levels were removed in version 4.x of PowerShell Universal. All logging is verbose regardless of appsettings.json.
Version 3.x Procedure (Quick method)
1. From the PowerShell Universal console, navigate to 'Settings', 'General', 'Diagnostics'.
2. Click 'Download Logs' to download a .zip file containing the logs.
3. Attach the .zip to your case (ticket) once you raise one using the 'Contact Us' dialog of the Ironman Software home page.
Version 3.x Procedure (Advanced method)
1. From the PowerShell Universal console, navigate to 'Settings', 'General', 'Diagnostics'.
2. Change the logging levels to Debug for both 'Log Level' and 'Microsoft Log Level'
3. Take your time to recreate the issue for which you are gathering logs. Note the time ⌚ at which the error occurred.
4. Click 'Download Logs' to download a .zip file containing the logs.
5. Attach the .zip to your case (ticket) once you raise one using the 'Contact Us' dialog of the Ironman Software home page.
6. Include as many details as possible, including the timestamp of when the error occurred.
7. Set the log level back to 'Information' and the Microsoft Log Level back to 'Warning'.