You can filter the Orchestrator server logs for a specific workflow run and collect diagnostic data about the workflow run.

About this task

The Orchestrator logs contain a lot of useful information, but not every log entry has diagnostic context. When multiple instances of the same workflow are running at the same time, you can track the different workflow runs by filtering the diagnostic data about each run in the Orchestrator logs.


  1. Log in as an administrator to the machine on which the Orchestrator server is installed.
  2. Navigate to the log4j.xml file and open it in a text editor.



    If you installed the standalone version of Orchestrator

    Go to install_directory\VMware\Orchestrator\app-server\conf\log4j.xml.

    If the vCenter Server installed Orchestrator

    Go to install_directory\VMware\Infrastructure\Orchestrator\app-server\conf\log4j.xml.

  3. Find the following entry:
    <layout class="org.apache.log4j.PatternLayout"> <param
    name="ConversionPattern" value="%d{yyyy-MM-dd HH:mm:ss.SSSZ} %-5p
    [%c{1}] %m%n"/> </layout>
  4. Change the conversion pattern.
    <layout class="org.apache.log4j.PatternLayout"> <param
    name="ConversionPattern" value="%d{yyyy-MM-dd HH:mm:ss.SSSZ} %-5p
    [%c{1}][%X{value_name}] %m%n"/> </layout>

    Where value_name is the name of the available diagnostic values. The possible names are:




    The name of the user who started the workflow


    The name of the running workflow


    The ID of the running workflow


    The token of the running workflow


    The workflow ID and token, separated by a colon


    The name of the user who started the workflow, the name of the running workflow, the workflow ID, and the workflow token, separated by colons.

  5. Save and close the file.


The Orchestrator logs are filtered according to the changes you made to the file.