Using the MOB to Explore the DiagnosticManager

You can access the DiagnosticManager using the MOB. See Managed Object Browser.

To explore DiagnosticManager

1	Start the mob by typing the MOB URL (https://hostname.yourcompany.com/mob) into a Web browser.

2	In the ServiceContent data object, click the link (ha-diagnosticmanager or DiagMgr) in the Value column for the diagnosticManager property, to navigate to the DiagnosticManager for the system.

■	For ESX/ESXi, ha-diagnosticsmanager is the managed object ID.

■	For vCenter Server, DiagMgr is typically the managed object ID.

3	Click the link to the reference to display the managed object reference to the DiagnosticManager in the MOB.

DiagnosticManager provides three operations that allow you to obtain information about the descriptions currently available in the log file and log file content.

Because DiagnosticManager can track multiple ESX/ESXi systems, you can use the QueryDescriptions operation to return the names of keys used for all hosts. From this array, select the key for the host from which you want to obtain the log file.

4	On QueryDescriptions, click the Invoke Method link.

The vCenter Server system returns the contents of the log file for the selected host as a string array for the lineText property of DiagnosticManagerLogHeader.

The string array returned through the MOB in this way is the content of the log file. The content contained in the log file is the same content that is available through the following other mechanisms:

■	Displayed in the vSphere Client

■	Included in a diagnostic bundle created through the DiagnosticManager.GenerateLogBundles_Task method.

■	Available in the hostd.log file

■	Returned to a client application that you write