Log Parser Plugin

The Log Parser plugin parses log files on the Deployment Automation agent side and provides an output log file with the results.

Use this plugin to parse log files from products that you are executing through your process steps. For example, to put a conditional step in your process to check for a specific completion code that is stored in a log, you can use Log Parser to do that.

The agent processes logs as follows:

Logs are uploaded to the server after each step is executed and are stored on the agent side until the whole process is finished.
The log file for each step has a distinct path to avoid conflicts with any other process running on the agent at the same time.
Deployment Automation will not prevent deletion of the log files of a currently running process. If this situation occurs, the deleted files will be skipped during the log file deletion operation in the end of the process execution.

The following built-in properties are used as the default value for Include Files in the Log Parser steps:

The prevStep property enables you to access previous step values without having to explicitly fill in the previous step name. You can provide a property expression in the following format where prevStep will resolve to the value of the previous step name during execution of the process.
${p:prevStep/propName}

All properties of the previous step that are accessible with the full syntax are accessible through the prevStep property.

Warning: If a step has multiple possible previous steps in a conditional process design, the results will be unpredictable.

The logPath property is an output property that resolves to the full path of a given step's log file during process execution. If you specify the property expression in the following format, the values will resolve to the value of the previous step name and the log path for that step during execution of the process:
${p:prevStep/logPath}

Important: This functionality was introduced in Deployment Automation version 5.1.5. Processes that were executed before this functionality was implemented will not have the logPath property.

In the Process Editor Available Plugin Steps, navigate to Utilities > LogParser.

This plugin has the following steps for you to add to your processes: