Leanring about your Workspace ONE UEM component logging allows your to better analyze and correct any issues you may have. Sometimes seeing examples of log files can greatly enhance your ability to understand its importnace while providing use cases on how to best use the information provided.

Best practices help piece together information by providing examples of how to use logging when troubleshooting or analyzing an issue with either a core component or an integrated component.

Capture Logs

Capturing accurate verbose logs helps diagnose errors and disconnections in your deployment.

  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.

    1. Changing the filename ensures that the log is not overwritten.

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

  3. Reproduce the event that cause the error, for example, an authentication failure.

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

    1. 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.

Performance Logging

Explore and implement additional logs to troubleshoot and improve your Workspace ONE UEM deployment.

Some logging may require additional components or requirements to gather.

Table 1. Third-Party SDK App Logs

Method/Folder

Log Name

Description

ADB/Android Studio/RXLogger

*.txt

Contains real time logs for SDK application logging from developer run application.

Console app on macOS

*.txt

Contains real time logs for SDK application logging from developer run application.

Console (Apps&Book\Analytics\App Logs)

AppLog####.txt

Contains information from third-party SDK application integrations.