About Action Logging

To streamline diagnoses of issues, OTM supports a type of logging called Action Logging. When running a finder/manager action, editing a top-level record or submitting a process control action, you can opt to turn on a log dedicated to that action. While the action runs, all logging needed for diagnostics is written out to a single, specific log file. When the action completes, you can view the focused log and download it for offline analysis.

Action logs are built on the Log File infrastructure available to shared logs in OTM:

1. An action log includes, by default, all IDs necessary for proper diagnosis of the specific action run.
2. An action log includes all logging from the initiation of the action to its completion. This includes related, asynchronous work like agents. It is written to a single file with no cycling.
3. IDs used by an action log are only enabled while the action is running. Impact on system performance due to enabled log IDs is limited to the duration of the action.

The key to triggering an action log is specifying a Log Profile to run during action execution. The log profile defines a set of log IDs to be active during the action. Some of these IDs can be active only while certain code subcomponents of the action are running. The profile consists of:

• A set of Log IDs, to be collected while the action is running.
• A set of Log Components. Each log component defines a set of Log IDs to be collected while a particular subcomponent of the action, known as a Log Component Type, is running.