Instead of using the vSphere Web Client log file, you can create a separate log file for the vCloud Air plug-in that contains only the plug-in's log information. The plug-in log file is stored in the same location as the vSphere Web Client log file.

You can choose to save log information in the plug-in log file only or in both the plug-in log file and the vSphere Web Client log file, vsphere_client_virgo.log.

Both log files are available in the following location.

Operating System

Log File Location

Linux

/usr/lib/vmware-vsphere-client/server/serviceability/logs

Windows

C:\ProgramData\VMware\vSphere Web Client\serviceability\logs

Note

The location of the VMware directory might vary based on the Windows OS version. Look for the VMware directory in the Application Data or Program Data folder.

You can customize the name of the plug-in log file.

You can also specify the level of information to be logged in the plug-in log file. The default level is INFO. Use DEBUG if you are sending logs to VMware technical support.

1

Go to the vSphereWebClientInstallDir/vmware-vsphere-client/server/configuration directory.

On Linux, vSphereWebClientInstallDir is typically /usr/lib/.

2

Open the serviceability.xml file for editing.

3

Add the following <appender> element to the file, after the last <appender> element.

<!-- Creating an appender for logging. All vCloud Air logging is routed through this xml. -->

  <appender name="VCLOUDAIR_LOG_FILE"
                              class="ch.qos.logback.core.rolling.RollingFileAppender">
                   <!-- Relative path(To virgo Server) where the logs are saved. -->
                 <file>serviceability/logs/vCloudAir.log</file>
                <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
                       <FileNamePattern>serviceability/logs/vCloudAir_%i.log.zip</FileNamePattern>
                      <MinIndex>1</MinIndex>
                     <MaxIndex>4</MaxIndex>
              </rollingPolicy>

          <triggeringPolicy
                             class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
                    <MaxFileSize>10MB</MaxFileSize>
           </triggeringPolicy>
          <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">
         <!-- Pattern for log entries in the log file -->
                    <Pattern>[%d{yyyy-MM-dd HH:mm:ss.SSS}] [%-5level] %-28.28thread
                               %X{sessionGuid} %-64.64logger{64} %X{medic.eventCode} %msg %ex%n
                    </Pattern>
        </encoder>
  </appender>

To customize the name of the log file, change the name in the <file> element and the <FileNamePattern> element above.

4

Add the following <logger> element to the file, after the last <logger> element.

<logger level="INFO" additivity="false" name="com.vmware.vcim">
                        <appender-ref ref="VCLOUDAIR_LOG_FILE" />
          </logger>
5

If you want log information to be stored in the vSphere Web Client log file in addition to the plug-in log file, in the new <logger> element change additivity="false" to additivity="true".

6

If you want to change the log severity level for the file from the default INFO, in the new <logger> element change the value of logger level="INFO".

You can change it to "ERROR", "WARN", or "DEBUG".

7

Restart the vSphere Web Client.

On Linux, use this command.

service vsphere-client restart

On Windows, use this command.

sc restart vspherewebclientsvc