Providing Other Diagnostic Logs for CloudM Migrate

Windows Event Logs provide a system-wide record of application and system behavior. These are essential for diagnosing errors related to memory, permissions, or system-level failures.

1. On your migration server, open the Event Viewer (search for "Event Viewer" in the Windows Start Menu).
2. In the left-hand pane, expand the Windows Logs folder.
3. Export Application Events:
   • Right-click on the Application log.
   • Select Save All Events As....
   • Name the file (e.g., Application_Logs.evtx) and click Save.
4. Export System Events:
   • Right-click on the System log.
   • Select Save All Events As....
   • Name the file (e.g., System_Logs.evtx) and click Save.
5. Attach both .EVTX files to your support ticket.

These logs are crucial for diagnosing database issues, such as connection failures or data-writing errors.

1. Open File Explorer on your PostgreSQL server.
2. Navigate to the log directory. By default, this is located at:
   C:\Program Files\PostgreSQL\<VERSION>\data\log

   Note: Replace <VERSION> with your specific version number (e.g., 14, 15). If you installed PostgreSQL to a custom path, navigate to that location instead.

3. Right-click on the log folder.
4. Select Send to > Compressed (zipped) folder.
5. Attach the resulting .zip file to your support ticket.

Redis is used for caching within CloudM Migrate. These logs help identify performance bottlenecks or caching failures.

1. Open File Explorer on your migration server.
2. Navigate to the Redis installation directory, typically located at:
   C:\Program Files\Redis
3. Locate the Logs folder.
4. Right-click the folder and select Send to > Compressed (zipped) folder.
5. Attach the resulting .zip file to your support ticket.

For issues involving network connectivity or API communication errors, we may require a full HTTPS trace using Fiddler.

• For detailed instructions on capturing these logs, please refer to our dedicated guide: How to Capture a Fiddler Trace for Troubleshooting