...
The monitoring stream handles continuous execution check and check for stuck workflows (workflows which execution takes longer than expected). Parameters for this checks are set in *.spf profiles described below.
SPF Profiles
Example of an *.spf profile contents:
...
- unit is a special parameter, works as a pointer on type of the include in case of new alerts processing;
- workflow is workflow name;
- type sets the type of processing ;
- timeperiod is time period in seconds;
- timethreshold is processing limit in seconds;
- error_prefix sets default type of alerts for this workflow;
- notificationemail is default email for notifications;
- patterns switches on/off sending alerts
Processing Details
Query
All new code will be in read_workflow_profiles.inc. This include will execute executes the following sql query from the start.:
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Result of this query is all necessary information about launched workflows (except for already processed).
Result of the query All this is loaded to a file .After that include check existing and then include checks existing *.spf profiles in ml2-0_cm_profiles folder.
...
Alerts processing
All Alert processing will use uses methods from the time utils include. Every workflow from profile will be looked for in A search in the query results file is performed for every workflow in the profile. For periodic alerts last workflow with name from profile will be is checked through by update_date and current time values difference and if the difference will be is greater than timeperiod parameter – this workflow will be write down in is written down into current event array. For stuck workflow alerts type all processing workflows will be checked and if theirs processing time will be greater than timethreshold – it will be also write down in the current event array.
...
Every line in current event array will be parsed. With create_tsr.inc TSR with necessary information will be created. Type of the TSR message will be choosed is chosen from current event line time variables type.
...
Eas_distribution changes
TSR parsing
For parsing the incoming TSR TSRs tsr_to_w_state.inc will be usedis used. This include file transform 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 task parameter AlertNotificationEmail (this parameter is unique!) . If this parameter is exist – it will be used as email address, if parameter doesn’t exist include will use address from description or default email.
...