Collecting diagnostic information for App Volumes
search cancel

Collecting diagnostic information for App Volumes


Article ID: 345386


Updated On:




VMware Technical Support routinely requests diagnostic information from you when a support request is addressed. This diagnostic information contains product specific logs and configuration files from the host on which the product is run. This information is gathered using a specific script or tool within the product.

This article provides procedures for obtaining diagnostic information for App Volume components.
The diagnostic information obtained by using this article is uploaded to VMware Technical Support. To uniquely identify your information, use the Support Request (SR) number you receive when you create the new SR.

For more information on:


App Volumes consists of these components:

  • App Volumes Manager
  • App Volumes Agent
App Volumes Agent
To collect App Volumes Agent logs, you can navigate to the respective log file locations on the Agent machines.

The svservice.log file can be found at C:\Program Files (x86)\CloudVolumes\Agent\Logs, while the svdriver.log file is saved in ETL format at C:\Windows\System32\LogFiles\WMl\AppVolumesAgent.etl.

To convert the ETL log file to XML format for easier viewing, follow these steps:
  • Open a command prompt from the App Volumes Agent machine.
  • Run the command "logman update AppVolumesAgent -fd –ets" to flush the buffers and ensure the Agent transaction data is saved to disk.
  • Then, run the command "tracerpt.exe AppVolumesAgent.etl -of xml -gmt -tp "C:\Program Files (x86)\CloudVolumes\Agent\tmf" -o AppVolumesAgent.xml" to convert the ETL log to XML format.
  • You can now open the XML file with MS Excel for easier analysis.
Note: The above details are specific to the App Volumes Agent logs.

App Volumes Manager

To obtain diagnostic information from the App Volumes Manager, we have a new process to generate the logs from App Volumes Manager UI for App Volumes 4.x and 2.18.x.
  • From App Volumes Manager, go to ACTIVITY > Troubleshooting and click Create.
  • On the Create Troubleshooting Archive window, select the configuration data and log files you want to archive.Click Create.  By default, the files are saved in C:/Program Files (x86)/CloudVolumes/Manager/public/troubleshooting on the current serve

App Volumes Manager logs can also be collected remotely.
Documentation on how to create an API session can be found here:

Additional Information

Uploading diagnostic information for VMware
Increasing Logging Level for AppVolumes Manager
AppVolumes 4.0 Manager Log Procedure

Attachments get_app get_app