Each peripheral component handles logging differently from the core components handled by the Workspace ONE UEM console. You must access each component server to change the logging level.

Important:

After you finished troubleshooting, revert the logging level back to Disabled to preserve hardware resources.

VMware Enterprise Systems Connector (ACC)

To change the logging level for the ACC service:

  1. Access the CloudConnector.exe.config file contained in the /Airwatch/CloudConnector/Bank# folder.
  2. Make sure you compare the two bank folders to ensure you are editing the one with the most recent modified dates.
  3. Change the level from error to verbose in the line <loggingConfiguration> line.
  4. Allow the services a few minutes to pick up the logging change.

Classic Secure Email Gateway (SEG)

Change the Logging Level for the EASListener Service

  1. Access the SEG service page contained at http://localhost/segsetup.
  2. Select Verbose from the logging level box.
  3. Select Save.
  4. Wait a few minutes for the EASListener to pick up the logging change.

Change the Logging Level for the EASintegration Service

  1. Access the AW.EAS.IntegrationService.exe.config file contained in the /AW.Eas.IntegrationService folder.
  2. Change the level from Error to Verbose in the <loggingConfiguration> line.
  3. Wait a few minutes for the service to pick up the logging change.

Change the Logging Level for the SEG Setup Service

  1. Access the Web.config file contained in the /AW.Eas.Setup folder.
  2. Change the level from Error to Verbose in the <loggingConfiguration> line.
  3. Wait a few minutes for the service to pick up the logging change.

Change the Logging Level for the Kerberos Service

  1. Access the AirWatch.Kerberos.AuthService.exe.config file contained in the /AirWatch.KCD.AuthService folder.
  2. Change the level from Error to Verbose in the <loggingConfiguration> line.
  3. Wait a few minutes for the service to pick up the logging change.

Enable SEG Targeted Logging for Devices

  1. Access the admin page at https://localhost/SEGconsole/.
  2. Under Targeted Logging, select EAS device Identifier or Username and select Add Target.
  3. Select Enter Additional Details and Add Target if you need additional information.
  4. Select Start Targeted Logging to begin.
  5. Once reproduction is complete, select Stop Targeted Logging. By default, logs are written to the Logs > EASListener Folder.

Secure Email Gateway v2 (SEGv2)

To change the logging levels for the SEGv2 service:

  1. Access the admin page at https://localhost:44444/seg/admin.
  2. In the Logging tab, change the logging level from Error to Debug.
  3. Wait a few minutes for the service to pick up the logging change.

Email Notification Service

To change the logging levels for the integration service:

  1. Access the AW.Mail.Notification.Service.Config file contained in the Installation folder.
  2. Change the level from Error to Verbose in the application configuration.
  3. Wait a few minutes for the service to pick up the logging change.

Email Notification Service v2

By default, ENSv2 runs at the most verbose level of logging.

VMware Tunnel

To change the logging levels for VMware Tunnel, in the Workspace ONE UEM console, navigate to Groups & Settings > All Settings > System > Enterprise Integration > VMware Tunnel > Configuration > Advanced .

AirWatch Content Gateway

To change the logging levels for the Content Gateway:

  1. Access the logback.xml file contained in the Content Gateway Config folder.
  2. Change the level to debug in the <logger name="com.airwatch" level="info" /> line.
  3. Wait a few minutes for the service to pick up the logging change.

Unified Access Gateway

To change the logging levels for the Unified Access Gateway service:

  1. In the Unified Access Gateway Admin UI, navigate to Support Settings > Log Level Settings.
  2. Select INFO, ERROR, WARNING, or DEBUG based on your requirements.
    Level Type of Information Collected
    INFO Information messages that highlight the progress of the service.
    ERROR Error events that might still allow the service to continue running.
    WARNING Potentially harmful situations but are usually recoverable or can be ignored.
    DEBUG Events that would generally be useful to debug problems. You can enable the debug mode to view or manipulate the internal state of the appliance. The debug mode lets you test the deployment scenario in your environment.
  3. Wait a few minutes for the service to pick up the logging change.

Remote File Storage

To change the logging levels for Remote File Storage:

  1. Access the logback.xml file contained in the RFS Configuration Folder.
  2. Edit the file on using the Linux vi editor or on WinSCP:
  3. Edit the logback.xml file:
    1. Enter i to begin writing text.
    2. Change the logging level XML attribute value in both the logger and root XML elements.
    3. Select Esc to exit edit.
    4. Press wq! to write and quit.
  4. Save changes and restart each service.

Content Rendering Engine

To change the logging levels for the Content Rendering Engine:

  1. Access the logback.xml file contained in the CRE Configuration Folder.
  2. Edit the file on using the Linux vi editor or on WinSCP:
  3. Write text in the logback.xml file:
    1. Enter i to begin writing text.
    2. Change the logging level XML attribute value in both the logger and root XML elements.
    3. Select Esc to exit edit.
    4. Press wq! to write and quit.
  4. Restart each service after saving changes.

VMware Identity Manager Service

To change the logging level for the VMware Identity Manager Service in the Workspace ONE UEM console, navigate to Groups & Settings > All Settings > Admin > Diagnostics > Logging.

VMware Identity Manager Connector (ESC)

To change the logging levels for the VMware Identity Connector:

  1. Access the l hc-log4j.properties file contained in /usr/local/horizon/conf/ .
  2. Add “log4j.rootLogger=DEBUG,rollingFile,SYSLOG” to the first line of the file.
  3. Wait a few minutes for the service to pick up the logging change.

Workspace One Intelligence

By default, Workspace ONE Intelligence (ETL) runs at the most verbose level of logging.

Adaptiva

By default, Adaptiva runs at the most verbose level of logging.

Memcached

By default, Memcached runs at the most verbose level of logging.