Error message formatting

A log file is created in the BASEDIR/smarts/local/logs directory for each domain manager application started with the --output option. (Any domain manager 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 application, and for resolving application and discovery errors.

VMware Telco Cloud Service Assurance exception message formatting shows through example the formatting structure of error (exception) messages that are written to a log file.

Figure 1. VMware Telco Cloud Service Assurance exception message formatting

The first line of an error message identifies the following information:

• Domain manager software subsystem that reported the error

• Severity level of the error:

  • F for Fatal

  • E for Error

  • W for Warning

  • N for Notice

  • I for Informational

  • D for Debug

• Name of the error table from which the domain manager subsystem took the error

• Name of the error

  In the example error message, the reporting subsystem is ASL, for Adapter Scripting Language, the message severity level is Warning, the error table name is ERROR_RULE_SOURCE, and the error name is “While executing rule set.” The combination of an error table name and an error name uniquely identifies a particular error.

  The remaining lines in an error message, referred to as chained exceptions, provide more detail about the exception appearing in the top line. The last chained exception identifies the root cause of the error. In VMware Telco Cloud Service Assurance exception message formatting, the root cause of the error is that the code was instructed to access a class that the code could not find.

  Some VMware Telco Cloud Service Assurance subsystems and their descriptions identifies and briefly defines some of the domain manager subsystems.

Table 1. Some VMware Telco Cloud Service Assurance subsystems and their descriptions

VMware Telco Cloud Service Assurance subsystem	Description
ASL	Adapter scripting language subsystem. (Most Adapters are implemented in ASL code.) Generates errors detected by ASL code.
DNS	Network name translation subsystem.
DVST	Device status polling subsystem.
DX	Correlator subsystem.
ICF	Domain manager framework subsystem.
ICS	Domain manager service assurance subsystem.
MR	Repository manager. Throws generic Repository errors; the Repository is the database that stores the discovered topology (inventory).
OSA	Operating system accessor.
RTLD	Module loading. Throws errors due to configuration problems that cause the code to be unable to locate parts of itself.
TOPO	Topology subsystem.
<SYS>	Not a subsystem; represents an operating system component that generated an error.