5.5

Table 8‑3. Orchestrator Log Files (Continued)
File Name Location Description
access.yyyy-mm-dd.log
n
If you installed Orchestrator standalone:
install_directory\VMware\Orchestrator\c
onfiguration\logs
n
If you installed Orchestrator with the
vCenter Server installer:
install_directory\VMware\Infrastructur
e\Orchestrator\configuration\logs
n
If you deployed the
Orchestrator Appliance: /var/log/vco/app-
server
This log lists the elements that are
needed to load and display the
pages of the Orchestrator
configuration interface. It keeps a
history of the actions that were
taken during the configuration of
Orchestrator and the time when
they were completed. However,
the log does not display the value
of the changed parameters. Use
this log to identify changes in the
behavior of the Orchestrator
server after a restart.
wrapper.log
n
If you installed Orchestrator standalone:
install_directory\VMware\Orchestrator\a
pp-server\bin
n
If you installed Orchestrator with the
vCenter Server installer:
install_directory\VMware\Infrastructur
e\Orchestrator\app-server\bin
Provides information from the
server.log file. Use this log to
check whether the VMware
vCenter Orchestrator Server
service was started by the
wrapper or by a user.
vCenter_Orchestrator_InstallLo
g.log
Check the file location in the message. This log is created when you
cancel the Orchestrator
installation or when the
installation fails.
Logging Persistence
You can log information in any Orchestrator script (workflow, policy, or action). This information has types
and levels. The type can be either persistent or non-persistent. The level can be DEBUG, INFO, WARNING, and
ERROR.
Table 8‑4. Creating Persistent and Non-Persistent Logs
Log Level Persistent Type Non-Persistent Type
DEBUG
Server.debug("short text", "long
text");
N/A
INFO
Server.log("short text", "long text"); System.log("text");
WARNING
Server.warn("short text", "long text"); System.warn("text");
ERROR
Server.error("short text", "long text"); System.error("text");
Persistent Logs
Persistent logs (server logs) track past workflow run logs and are stored in the Orchestrator database. To
avoid increasing the database infinitely, specify the number of logs stored per element (workflows and
policies) in the Orchestrator configuration interface. If you increase the default value of 50MB, the query
requires more space and time. To view server logs, you must select a workflow, a completed workflow run,
or policy and click the Events tab in the Orchestrator client.
Chapter 8 Additional Configuration Options
VMware, Inc. 89