The Embotics vCommander™ Windows service logs a great deal of information, which is typically used when interacting with Embotics’ technical support. An easy way to submit logs to the technical support team is to run the Embotics vCommander diagnostics.
Manually Managing Logging Level
You can also set DEBUG logging manually for individual components in the interest of keeping the log files current, and at a manageable size.
- On the Embotics vCommander application server, open <INSTALL_DIRECTORY>\Embotics\vCommander\tomcat\common\classes\log4j.properties using a text editor such as Notepad.
- Add the debug statement from those listed below to the file, making sure that there are no spaces preceding or trailing. Use lines only as directed by support to avoid increasing logging beyond the scope of what is needed to investigate your issue.
This line provides details about the security subsystem, and results in very active logging.
This line provides greater detail about interactions with directory services.
These lines provide verbose logging for guest OS scans, when used with the appropriate version of V-Commander®.
This line provides detailed statistics about the time taken to process events.
This line records the amount of time each event consumer takes to execute. A warning is already printed if this number exceeds 50 milliseconds.
This line prints information about event queue usage every 60 milliseconds.
This line provides logging for event creation, loading, and distribution.
This line logs details about information received from managed systems such as vCenter and SCVMM.
The second line above provides timing-only information without the very verbose details of the previous line.
This line provides statistics about the length of time taken for each method call.
This line provides verbose logging for cost operations.
This line provides details creating, deleting and working with policies.
This line provides details about policies triggering and resulting actions, including recommendations.
This line provides timing details for policy activity, including recommendations.
This provides overview details about the report service, not including logs output by specific reports being generated.
Logs output by specific reports as they are generated.
This line provide verbose logging for service request activity and processing.
This line provides details about messaging using simple mail transfer protocol.
This line provide greater logging for the general task subsystem, without details about specific tasks executing.
This line captures debug messages generated by specific tasks.
This line traces the workflow subsystem, including the submission and execution of workflow
log4j.logger.org.springframework.security.web=DEBUG log4j.logger.org.springframework.security.saml=DEBUG log4j.logger.com.embotics.vlm.portal.saml=DEBUG
These lines capture debug messages for SAML-based SSO solutions.
This line displays activity around VM naming, including name reservations.
This line displays the values retrieved and used in calculations to define capacity.
Run Program / Scripting
The following lines should be used together to debug issues with Run in Guest steps and scripting issues, when running against a local hypervisor:
log4j.logger.com.embotics.vlm.service.objectmodel=DEBUG log4j.logger.com.embotics.vlm.service.request=DEBUG log4j.logger.com.embotics.vlm.service.workflow=DEBUG
For the same debug against a public cloud, use:
The following line will expose how destinations are selected:
The following line will expose the details about creation and configuration of fenced services.