On the Configure Logs page in Control Center, you can set the level of server log and the scripting log that you require. If either of the logs is generated multiple times a day, it becomes difficult to determine what causes problems.

The default log level of the server log and the scripting log is INFO. Changing the log level affects all new messages that the server enters in the logs and the number of active connections to the database. The logging verbosity decreases in descending order.


Only set the log level to DEBUG or ALL to debug a problem. Do not use these settings in a production environment because it can seriously impair performance.

Log Rotation Settings

To prevent the server log from becoming too large, you can set the maximum file size and count of the server log by modifying the values in the Max file count and Max file size (MB) text boxes.

Orchestrator Log Files Export

From the Export Logs page in Control Center, you can generate a ZIP archive of troubleshooting information containing configuration, server, wrapper, and installation log files.

The log information is stored in a ZIP archive named vco-logs-date_hour.zip.


When you have more than one Orchestrator instance in a cluster, the ZIP archive includes the logs from all Orchestrator instances in the cluster.