9.1 vCloud Director for Service Providers
9.1.1 vCloud Director Cell Logs
The log location of vCloud Director for Service Provider components is described in the following table. In addition to these application logs, redirect the operating system logs to the centralized syslog as well, through the vRealize Log Insight Linux agent.
Table 14. VMware vRealize Operations Manager
Log Type | Location | Collection Method |
vCloud Director Info and debug logs | %VCLOUD%/logs/* | Periodic retrieval with %VCLOUD%/logs/vcloudcontainer-debug.log and %VCLOUD%/logs/vcloud-container-info.log. Most logs rotate with .1, .2, … extensions. While not for general use, these logs can be redirected to syslog by modification of the following properties file: %VCLOUD%/etc/log4j.properties |
vCloud Director syslog events | Sent through Syslog | Set syslog targets in %VCLOUD%/etc/global.properties and %VCLOUD%/etc/responses.properties |
vCloud Director system logs | Standard Linux log locations: /var/log/messages and /var/log/secure | Syslog targets through syslog.conf or agent retrieval |
To configure vCloud Director to forward log files to vRealize Log Insight
1. SSH into the vCloud Cells machine and open the following file to make setting changes:
/opt/vmware/vcloud-director/etc/log4j.properties
2. Near the bottom of the file, append the following code block. For the 10.10.10.250 entry on the second line, substitute the actual IP or hostname of the vRealize Log Insight cluster VIP.
3. In the code block, you can see that you can also control the level of logging being sent through to vRealize Log Insight by editing that last line and changing the threshold to WARN or CRITICAL.
4. Once that section has been added, go back to the top of the file and modify line 2 as shown here:
These entries add the source configured in step 2.
5. Save the file and restart the vmware-vcd service.
In examining source logs, log entries related to a specific customer can be identified using their organization id, that is part of vCloud Director log entry contains: currentContext.login.org.id=###
The following code block provides an example of the type of information included in a typical log file.
