Page Comparison

...

Alert processing uses methods from the time utils include. A search in the query results file is performed for every workflow in the profile. For periodic alerts last workflow with name from profile is checked by update_date and current time values difference and if the difference is greater than timeperiod parameter – this workflow is written down into current event array. For stuck workflow alerts type all processing workflows will be are checked and if theirs their processing time will be is greater than timethreshold – it will be is also write written down in the current event array.

TSR Generation

Every line in current event array will be is parsed. With create_tsr.inc  A TSR with necessary information will be createdis created by create_tsr.inc. Type of the TSR message is chosen from current event line time variables type.

<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="TaskStatusResponse" eaglemlVersion="2-0"  xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" eaglemlType="TaskStatusResponse">
<header><messageId>B810J250HIKUOGBG</messageId>
 <sentBy>monitoring</sentBy>
 <sendTo>eas_distribution</sendTo>
<creationTimestamp></creationTimestamp>
</header>
<statusItem>
<taskIdentifier>
 <correlationId>84040C2ADCC6D46</correlationId>
 <businessTaskId>B810J250HCFFDWIC</businessTaskId>
 </taskIdentifier>
 <status>REPORTING</status>
 <severityCode>1</severityCode>
<reason>
 <reasonTypeEnum>INFO</reasonTypeEnum>
 <reasonCode>1</reasonCode>
 <description>==================================
PPFT3 PERIODIC ALERT: Workflow eagle_dkm_source_launcher didn't launch in time period 300 seconds. Last launch was in 20181009 091845 CorrId 84040C2ADCC6D46 AlertNotificationEmail:vmironov@eagleinvsys.com</description>
<reasonTag>PPFT3 PERIODIC ALERT</reasonTag>
</reason>
</statusItem>
</EagleML>

...

TSR Parsing Within eas_distribution

...

TSR parsing

For parsing incoming TSRs tsr_to_w_state.inc is used. This include file transforms incoming TSR with xslt translation to correlation Id and email address from error description (if the TSR has in description AlertNotificationEmail) and with correlation ID and get_w_state.inc get gets AlertNotificationEmail task parameter AlertNotificationEmail (this parameter is unique!) . If this parameter is exist exists – it will be is used as email address, if parameter it doesn’t exist, include will use uses the address from description or default email.

Result of this stage – new email address (if TSR was for new types of alerts).

New xslt translation patterns

...

Xslt Translation Patterns

Currently, there are four patterns (pattern to be used is defined by the keywords in error description):

1). PPFT3 PERIODIC ALERT

If error description contains keywords PPFT3 PERIODIC ALERT – this pattern will be used. This will make This pattern makes up a email with error description from TSR.

2). PPFT3 STUCK WORKFLOW ALERT

If error description contains keywords PPFT3 STUCK WORKFLOW ALERT – this pattern will be used. This will make This pattern makes up a email with error description from TSR.

3). PPFT3 ERROR

If error description contains keywords PPFT3 ERROR – this pattern will be used. This pattern will make This pattern makes up a email with all errors from all tasktasks, that it can get from the incoming TSR.

4). PPFT3 WARNING

If error description contains keywords PPFT3 WARNING – this pattern will be used. This pattern will make This pattern makes up a blank email subject , and eas_distribution will does not send emails with blank email subject