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.

  1. On the Embotics vCommander application server, open <INSTALL_DIRECTORY>\Embotics\vCommander\tomcat\common\classes\log4j.properties using a text editor such as Notepad.
  2. 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.

There’s no need to restart the vCommander Windows service when making these changes.

Debug Lines



Login Session Security

 

log4j.logger.com.embotics.vlm.service.security=DEBUG


 

This line provides details about the security subsystem, and results in very active logging.


Active Directory and LDAP

 

log4j.logger.com.embotics.vlm.service.security.userdirectory=DEBUG


 

This line provides greater detail about interactions with directory services.


Guest OS Scanning

 

log4j.logger.osscanner=DEBUG


 

These lines provide verbose logging for guest OS scans, when used with the appropriate version of V-Commander®.


Events Processing

 

log4j.logger.eventdistribution=DEBUG


 

This line provides detailed statistics about the time taken to process events.

 

log4j.logger.EventProducerExecutor=DEBUG


 

This line records the amount of time each event consumer takes to  execute. A warning is already printed if this number exceeds 50  milliseconds.

 

log4j.logger.EventStats=DEBUG


 

This line prints information about event queue usage every 60 milliseconds.

 

log4j.logger.com.embotics.vlm.service.event=DEBUG


 

This line provides logging for event creation, loading, and distribution.


VMM Interactions

 

log4j.logger.com.embotics.vlm.service.server.mediator=DEBUG


 

This line logs details about information received from managed systems such as vCenter and SCVMM.


Guest OS Customizations

 

log4j.logger.com.embotics.vlm.service.server.mediator=DEBUG


 

IP Pooling

 

log4j.logger.com.embotics.vlm.service.network=DEBUG


 


Observation Processing 

 

log4j.logger.observation=DEBUG
log4j.logger.observation.timing=DEBUG

 

The second line above provides timing-only information without the very verbose details of the previous line.


Method Timing

 

log4j.logger.MethodTiming=DEBUG


 

This line provides statistics about the length of time taken for each method call.


Costing

 

log4j.logger.com.embotics.vlm.service.cost=DEBUG


 

This line provides verbose logging for cost operations.


Policy & Recommendations

 

log4j.logger.com.embotics.vlm.service.policy=DEBUG


 

This line provides details creating, deleting and working with policies.

 

log4j.logger.ruleengine=DEBUG


 

This line provides details about policies triggering and resulting actions, including recommendations.

 

log4j.logger.ruleengine.timing=DEBUG


 

This line provides timing details for policy activity, including recommendations.


Reporting

 

log4j.logger.com.embotics.vlm.service.reports=DEBUG


 

This provides overview details about the report service, not including logs output by specific reports being generated.

 

log4j.logger.com.embotics.vlm.reports.type=DEBUG


 

Logs output by specific reports as they are generated.


Service Requests

 

log4j.logger.com.embotics.vlm.service.request=DEBUG


 

This line provide verbose logging for service request activity and processing.


SMTP integration

 

log4j.logger.com.embotics.vlm.service.smtp=DEBUG


 

This line provides details about messaging using simple mail transfer protocol. 


Tasks

 

log4j.logger.com.embotics.vlm.service.task=DEBUG


 

This line provide greater logging for the general task subsystem, without details about specific tasks executing.

log4j.logger.com.embotics.vlm.controller.task=DEBUG


 

This line captures debug messages generated by specific tasks. 


Workflows

 

log4j.logger.com.embotics.vlm.service.workflow=DEBUG


 

This line traces the workflow subsystem, including the submission and execution of workflow


Single Sign-on 

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.


VM Naming 

log4j.logger.com.embotics.vlm.service.objectmodel=DEBUG

 

This line displays activity around VM naming, including name reservations.


Capacity 

log4j.logger.capacity=DEBUG

 

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: 

log4j.logger.com.embotics.vlm.controller.task=DEBUG
log4j.logger.com.embotics.vlm.controller.task.gd=DEBUG

  

Destinations

The following line will expose how destinations are selected:


log4j.logger.com.embotics.vlm.service.destination=DEBUG

 

Fencing

The following line will expose the details about creation and configuration of fenced services.


log4j.logger.fencing=DEBUG