Capture Logs

Capturing accurate verbose logs helps diagnose errors and disconnections in your deployment. This information provides general guidance for how to capture logs. Use this information when you're troubleshooting a specific issue and need to generate a log for that issue.

For additional information on specific logs, see:

• Core Services Logging
• Integrated Services Logging
• Device-Side Workspace ONE Hub Logs

Procedure

1. Ensure that the logging is currently producing verbose entries after a logging level change. Verify that debug entries are logged to ensure that the correct logging levels have applied.

2. Rename the current log file to include the date and time the log was captured.

   Changing the filename ensures that the log is not overwritten.

   For Java based services, you must stop the service before renaming any files.

3. Reproduce the event that caused the error.

   Example: an authentication failure.

4. Rename the new log file with a description of the observed error.

   Add a –Description or –DateTime to help identify the contents of the log file.

5. Export the log file to a sharable location. If applicable, attach the log file to a support ticket.