A log file is created in the BASEDIR/smarts/local/logs directory for each VMware Smart Assurance application started with the --output option. (Any VMware Smart Assurance application installed as a service automatically has --output in its invocation.) The log file is the primary tool for tracking the startup and progression of an VMware Smart Assurance application, and for resolving application and discovery errors. The VMware Smart Assurance System Administration Guide provides complete information about VMware Smart Assurance message logging.

The first line of a message identifies the VMware Smart Assurance software subsystem, the severity level of the message (F for Fatal, E for Error, W for Warning, N for Notice, I for Informational, and D for Debug), and the name of the error table from which the VMware Smart Assurance subsystem took the error (the name between the two hyphens).

Some VMware Smart Assurance subsystems and their descriptions identifies and briefly defines some of the VMware Smart Assurance subsystems. Only the ASL subsystem messages indicate software errors. The other subsystem messages are informational.

Table 1. Some VMware Smart Assurance subsystems and their descriptions

VMware Smart Assurance subsystem



Adapter scripting language subsystem. (Most VMware Smart Assurance Adapters are implemented in ASL code.) Errors are detected by ASL code.


Network name translation subsystem


Device status polling subsystem


Correlator subsystem


VMware Smart Assurance framework subsystem


VMware Smart Assurance service assurance subsystem


Repository manager. Generates generic Repository errors; the Repository is the database that stores the discovered topology (inventory).


Operating system accessor


Module loading. Generates errors due to configuration problems that cause the code to be unable to locate parts of itself.




Not an VMware Smart Assurance subsystem; represents an operating system component that generated an error.