Page History

job

yes

Job in the current workflow for which log output should be analyzed

If the job occurs more than once in the workflow, the label argument must be specified.

no

Label of the job for which log output should be analyzed

If the job occurs more than once in the workflow, the label argument must be specified to identify the unique occurrence of the job..

yes

Regular expression used to analyze the log

The regular expression is applied to log output of the job.

Exampe 1: Identify lines with errors

Arguments:

pattern = ".*error.*"
log = "One line with error" + "\r\n" + "Line without the word" + "\r\n" + "And one line with error in the middle";

Return Variables:

• js7CheckLogMatches: One line with error|And one line with error in the middle
• js7CheckLogMatchedGroups:
• js7CheckLogMatchCount: 2
• js7CheckLogGroupCount: 0
• js7CheckLogGroupsMatchesCount: 0

Example 2: Identify Event IDs

Arguments:

pattern = "event:\d{3}";
log = "The first line with event:1234" + "\r\n" + "Line without event" + "\r\n" + "And one line with event:456 and event:555 in the middle";

Return Variables:

• js7CheckLogMatches: event:123|event:456|event:555
• js7CheckLogMatchedGroups:
• js7CheckLogMatchCount: 3
• js7CheckLogGroupCount: 0
• js7CheckLogGroupsMatchesCount: 0

Example 3: Identify dates

Arguments:

pattern = "\d{1,2}.\d{1,2}.\d{4}";
log = "1.2.2002: first line" + "\r\n" + "04.1.1888: second line" + "\r\n" + "22.11.2001: third line";

Return Variables:

• js7CheckLogMatchedGroups:
• js7CheckLogMatches: 1.2.2002|04.1.1888|22.11.2001
• js7CheckLogMatchedGroups:
• js7CheckLogMatchCount: 3
• js7CheckLogGroupCount: 0
• js7CheckLogGroupsMatchesCount: 0

Example 4: Identify dates

Arguments:

pattern = "(\d{1,2}.\d{1,2}.\d{4}).(.*)$";
log = "1.2.2002: first line" + "\r\n" + "04.1.1888: second line" + "\r\n" + "22.11.2001: third line";

Return Variables:

• js7CheckLogMatches: 1.2.2002: first line|04.1.1888: second line|22.11.2001: third line
• js7CheckLogMatchedGroups: 1.2.2002|04.1.1888|22.11.2001
• js7CheckLogMatchCount: 3
• js7CheckLogGroupCount: 0
• js7CheckLogGroupsMatchesCount: 6

no

Separator for matches

Executing the regular expression on log output can result in several matches that are returned from the js7CheckLogMatches or js7CheckLogMatchedGroups variables. Matches are separated from each other by the separator character. By default the pipe character | is used.

no

Maximum duration to read task history

When the CheckLogJob job is executed, the JOC Cockpit History may not yet have been added related results of the job execution to be analyzed.

Repeated calls are performed with a delay of 3s until a call is successful or the maximum duration specified for the timeout is reached whichever occurs first.

no

Handling log output as one line or as multiple lines

Enables multiline mode in which the expressions ^ and $ match just after or before, respectively, a line terminator or the end of the input sequence.

By default the expressions match the beginning and the end of the entire input sequence. Multiline mode can be enabled by the embedded flag expression (?m) too.

no

Handling of uppercase/lowercase

Enables case-insensitive matching. By default, case-insensitive matching assumes that only characters in the US-ASCII charset are being matched. Unicode-aware case-insensitive matching can be enabled by specifying the UNICODE_CASE flag in combination with this flag. Case-insensitive matching can be enabled via the embedded flag expression (?i) too. Specifying the flag may impose slight performance penalties.

false

no

Handling of line mode

This flag enables Unix line mode in which '\n' is used as a line terminator and ‘\r’ is treated as a literal character.

false