vSphere includes several logs, which you can access and customize. You can also use the DiagnosticManager service interface for troubleshooting. What to read next Troubleshooting Best PracticesApproach troubleshooting and problem-solving systematically, and take notes so you can trace your steps. Follow these guidelines to resolve issues with your client application. Overview of Configuration Files and Log FilesESXi and vCenter Server configuration files control the behavior of the system. Most configuration file settings are set during installation, but can be modified after installation. Log files capture messages generated by the kernel and different subsystems and services. ESXi and vCenter Server services maintain separate log files. The following table lists log files or reports, their locations and associated configuration files. Modifying the Log Level to Obtain Detailed InformationThe amount of information captured in the log files varies, depending on the level setting. Using DiagnosticManagerThe vSphere API provides access to the DiagnosticManager, the service interface for obtaining information from the log files and for generating diagnostic bundles. The logs are populated based on configuration settings, such as info, trivia, and so on. Using the MOB to Explore the DiagnosticManagerThe Managed Object Browser (MOB) is a graphical interface that allows you to navigate the objects on a server and to invoke methods. You can access the DiagnosticManager using the MOB. Generating Diagnostic BundlesTypically, customers create diagnostic bundles at the request of VMware technical support. Diagnostic bundles also allow developers to quickly obtain all configuration files and log files in a complete package.
