Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ElementElement descriptionDescription
Job Optional or multiple use allowed inside the NotificationObjects element  Restricts notifications for order or standalone jobs 
JobChainOptional or multiple use allowed inside the NotificationObjects elementRestricts notifications for job chains
TimerRefOptional or multiple use allowed inside the NotificationObjects elementRestricts notifications for performance checks (Timer)
Code Block
languagexml
titleExample
collapsetrue
<SystemMonitorNotification system_id="op5"> 
  <Notification> 
    <NotificationMonitor service_name_on_error="JobScheduler Monitoring Errors"> 
      ... 
    </NotificationMonitor> 
    <NotificationObjects>
      <!-- Send the job error, occurrent in the "test/my_job" order job, to the "JobScheduler Monitoring Errors" service. -->        
      <Job name="test/my_job" /> 
      <!-- Send the job chain error, occurrent in the "test/my_jobchain" job chain, to the "JobScheduler Monitoring Errors" service. --> 
      <JobChain name="test/my_jobchain" /> 
    </NotificationObjects> 
 </Notification> 
</SystemMonitorNotification>  

 

SystemMonitorNotification / Notification / NotificationObjects / Job 

Note:

This element specifies the order-controlled or standalone jobs for which notifications are being sent to a system monitor.

...

MasterMessageOptional or only once inside the NotificationObjects element

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJS-1837

Includes problems detected by a JobScheduler Master, e.g. database connection lost.

TaskWarningOptional or only once inside the NotificationObjects element

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJS-1837
 

 Includes job execution warning messages. 

TaskIfLongerThanOptional or only once inside the NotificationObjects element

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-522
 

Includes the feature to send notification in case that the execution of job requires a longer duration than expected.

TaskIfShorterThanOptional or only once inside the NotificationObjects element

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-

...

522

Includes the feature to send notification in case that the execution of job requires a shorter duration than expected.

Code Block
languagexml
titleExample
collapsetrue
<SystemMonitorNotification system_id="op5"> 
  <Notification> 
    <NotificationMonitor service_name_on_error="JobScheduler Monitoring Errors"> 
      ... 
    </NotificationMonitor> 
    <NotificationObjects>
      <!-- Send the job error, occurrent in the 

...

 

Job supports the following attributes:

AttributeUsageDescription
notifications

Optional

Integer

Specifies the number of transfers the same notification to a System Monitor.

Default: 1

scheduler_idOptional

Notifications are restricted to the JobScheduler instance with the given identification. By default notifications will be sent for all JobScheduler instances that log into the same database.

Regular expression can be used.

nameOptional

Job name including possible folder names.

Regular expression can be used.

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-353

return_code_from Optional Restricts notifications for jobs for a particular return code range. 
return_code_from Optional  Restricts notifications for jobs for a particular return code range.  
Code Block
languagexml
titleExample
collapsetrue
...
<Job notifications="2" name="test/my_job"/>
...
<Job scheduler_id="scheduler_4444" />
...
<Job scheduler_id="scheduler_4444" name="test/my_.*" />
... 
 order job, to the "JobScheduler Monitoring Errors" service. -->        
      <Job name="test/my_job" return_code_from="5"/> 
...  
<Job name=      <!-- Send the job chain error, occurrent in the "test/my_job" return_code_to="10"/>
...  
<Jobjobchain" job chain, to the "JobScheduler Monitoring Errors" service. --> 
      <JobChain name="test/my_jobjobchain" return_code_from="5" return_code_to="5"/>  
...
/> 
    </NotificationObjects> 
 </Notification> 
</SystemMonitorNotification>  

 

SystemMonitorNotification / Notification / NotificationObjects /

...

Job 

Note:

This element specifies the order-controlled or standalone jobs for which notifications are being sent to a system monitor.

Support for standalone jobs starting with

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-400
.

 

Job 

...

JobChain supports the following attributes:

AttributeUsageDescription
notifications

Optional

Integer

Specifies the number of transfers the same notification to a System Monitor.

Default: 1

scheduler_idOptional

Notifications are restricted to the JobScheduler instance with the given identification. By default notifications will be sent for all JobScheduler instances that log into the same database.

Regular expression can be used.

nameOptional

Job chain name including possible folder names.

Regular expression can be used.

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-353

return_code_from Optional Restricts notifications for job chains  for jobs for a particular return code range. 
return_code_from Optional  Restricts notifications for job chains for jobs for a particular return code range.  
step_fromOptionalRestricts notifications for job chains to a sequence of job nodes that are specified with the step_from and step_to attributes.
step_toOptionalRestricts notifications for job chains to a sequence of job nodes that are specified with the step_from and step_to attributes.
excluded_stepsOptionalSpecifies the steps which will be excluded from the analyzing (separated by semicolon)
Code Block
languagexml
titleExample
collapsetrue
...
<Job notifications="2" 
Code Block
languagexml
titleExample
collapsetrue
...
<JobChain notifications="2" name="test/my_jobchainjob"/>
...
<JobChain<Job scheduler_id="scheduler_4444" />
...
<JobChain<Job scheduler_id="scheduler_4444" name="test/my_.*" />
... 
<JobChain<Job name="test/my_jobchainjob" return_code_from="5"/> 
...  
<JobChain<Job name="test/my_jobchainjob" return_code_to="10"/>
...  
<JobChain<Job name="test/my_jobchainjob" return_code_from="5" return_code_to="5"/>  
...
<JobChain name="test/my_jobchain" step_from="200"/>
...
<JobChain name="test/my_jobchain" step_to="500"/>
...
<JobChain name="test/my_jobchain" step_from="300" step_to="300"/>
...
<JobChain name="test/my_jobchain" excluded_steps="200;300"/>
...

 

SystemMonitorNotification / Notification / NotificationObjects / TimerRef

TimerRef supports the following attributes:

AttributeUsageDescription
notifications

Optional

Integer

Specifies the number of transfers the same notification to a System Monitor.

Default: 1

refOptionalCorresponds with Timer name setting defined in the SystemMonitorNotification / Timer element
notify_on_error

 

Optional

Boolean

Send timer check notification when the configured job chain contains the error notifications.

Default: false

 

SystemMonitorNotification / Notification / NotificationObjects / JobChain

JobChain supports the following attributes:

AttributeUsageDescription
notifications

Optional

Integer

Specifies the number of transfers the same notification to a System Monitor.

Default: 1

scheduler_idOptional

Notifications are restricted to the JobScheduler instance with the given identification. By default notifications will be sent for all JobScheduler instances that log into the same database.

Regular expression can be used.

nameOptional

Job chain name including possible folder names.

Regular expression can be used.

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-353

return_code_from Optional Restricts notifications for job chains  for a particular return code range. 
return_code_from Optional  Restricts notifications for job chains for a particular return code range.  
step_fromOptionalRestricts notifications for job chains to a sequence of job nodes that are specified with the step_from and step_to attributes.
step_toOptionalRestricts notifications for job chains to a sequence of job nodes that are specified with the step_from and step_to attributes.
excluded_stepsOptionalSpecifies the steps which will be excluded from the analyzing (separated by semicolon)
Code Block
languagexml
titleExample
collapsetrue
...
<JobChain notifications="2" name="test/my_jobchain"/>
...
<JobChain scheduler_id="scheduler_4444" />
...
<JobChain scheduler_id="scheduler_4444" name="test/my_.*" />
... 
<JobChain name="test/my_jobchain" return_code_from="5"/> 
... 
<JobChain name="test/my_jobchain" return_code_to="10"/>
... 
Code Block
languagexml
titleExample
collapsetrue
<SystemMonitorNotification system_id="op5"> 
  <Notification> 
    <NotificationMonitor service_name_on_error="JobScheduler Monitoring Error"> 
      ... 
    </NotificationMonitor> 
    <NotificationObjects> 
     <!-- 
     Send the job chain error, occurring in the "test/my_jobchain" job chain, to the "JobScheduler Monitoring Errors" service. 
     --> 
     <JobChain name="test/my_jobchain" return_code_from="5" return_code_to="5"/> 
    </NotificationObjects> 
  </Notification>   
 
  <Notification> 
    <NotificationMonitor service_name_on_error="JobScheduler Monitoring Performance"> 
      ... 
    </NotificationMonitor> 
    <NotificationObjects> 
      <!-- 
      Sends the performance check error, occurring in the 
...
<JobChain name="test/my_jobchain" step_from="200"/>
...
<JobChain name="test/my_jobchain" step_to="500"/>
...
<JobChain name="test/my_jobchain" job chain, to the "JobScheduler Monitoring Performance" service. 
      Sends the performance check error to the "JobScheduler Monitoring Performance" service will be ignored when the "step_from="300" step_to="300"/>
...
<JobChain name="test/my_jobchain" excluded_steps="200;300"/>
...

 

SystemMonitorNotification / Notification / NotificationObjects / TimerRef

TimerRef supports the following attributes:

AttributeUsageDescription
notifications

Optional

Integer

Specifies the number of transfers the same notification to a System Monitor.

Default: 1

refOptionalCorresponds with Timer name setting defined in the SystemMonitorNotification / Timer element
notify_on_error

 

Optional

Boolean

Send timer check notification when the configured job chain contains the error notifications.

Default: false

Code Block
languagexml
titleExample
collapsetrue
<SystemMonitorNotification system_id="op5"> 
  <Notification> 
    <NotificationMonitor service_name_on_error="JobScheduler Monitoring Error"has the job chain error (default notify_on_error = false). 
      --> 
      <TimerRef ref="my_timer" /> ... 
    </NotificationObjects>NotificationMonitor> 
 </Notification>     <NotificationObjects> 
     <!-- 
 <Timer name="my_timer"> 
     Send the job chain error, occurring in the "test/my_jobchain" job chain, to the "JobScheduler Monitoring Errors" service. 
     --> 
     <TimerJobChain<JobChain name="test/my_jobchain" /> 
    </Timer> 
</SystemMonitorNotification> 

 

NotificationObjects> 
  </Notification>   
 
  <Notification> 
    <NotificationMonitor service_name_on_error="JobScheduler Monitoring Performance"> 
      ... 
    </NotificationMonitor> 
    <NotificationObjects> 
      <!-- 
      Sends the performance check error, occurring in the "test/my_jobchain" job chain, to the "JobScheduler Monitoring Performance" service. 
      Sends the performance check error to the "JobScheduler Monitoring Performance" service will be ignored when the "test/my_jobchain" has the job chain error (default notify_on_error = false). 
      --> 
      <TimerRef ref="my_timer" /> 
    </NotificationObjects> 
 </Notification>   
 
 <Timer name="my_timer"> 
    <TimerJobChain name="test/my_jobchain" /> 
 </Timer> 
</SystemMonitorNotification> 


SystemMonitorNotification / Notification / NotificationObjects / MasterMessage

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJS-1837

MasterMessage includes problems detected by a JobScheduler Master, e.g. database connection lost.

Requirements:

  •   ./config/factory.ini configuration file:
    • mail_queue_only=true

    • mail_queue_dir setting specifies a directory to store the JobScheduler mails

    • mail_on_warning=true

    • mail_on_error=true

MasterMessage supports the following attributes:

AttributeUsageDescription
scheduler_idOptional

Notifications are restricted to the JobScheduler instance with the given identification. By default notifications will be sent for all JobScheduler instances that log into the same database.

Regular expression can be used.

notifications

 

Optional

Integer

Specifies the number of transfers the same notification to a System Monitor.

Default: 1


SystemMonitorNotification / Notification / NotificationObjects / TaskWarning

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJS-1837

TaskWarning includes job execution warning messages.

Requirements:

  •  ./config/factory.ini configuration file:
    • mail_queue_only=true

    • mail_queue_dir setting specifies a directory to store the JobScheduler mails

    • mail_on_warning=true

TaskWarning supports the following attributes:

AttributeUsageDescription
scheduler_idOptional

Notifications are restricted to the JobScheduler instance with the given identification. By default notifications will be sent for all JobScheduler instances that log into the same database.

Regular expression can be used.

notifications

 

Optional

Integer

Specifies the number of transfers the same notification to a System Monitor.

Default: 1


SystemMonitorNotification / Notification / NotificationObjects / TaskIfLongerThan

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-522

TaskIfLongerThan includes the feature to send notification in case that the execution of job requires a longer duration than expected.

Requirements:

  • The Job configuration contains the warn_if_longer_than setting.  
  • ./config/factory.ini configuration file:
    • mail_queue_only=true

    • mail_queue_dir setting specifies a directory to store the JobScheduler mails

    • mail_on_warning=true

TaskIfLongerThan supports the following attributes:

AttributeUsageDescription
scheduler_idOptional

Notifications are restricted to the JobScheduler instance with the given identification. By default notifications will be sent for all JobScheduler instances that log into the same database.

Regular expression can be used.

notifications

 

Optional

Integer

Specifies the number of transfers the same notification to a System Monitor.

Default: 1

 

SystemMonitorNotification / Notification / NotificationObjects / TaskIfShorterThan

 

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-522

 TaskIfShorterThan includes the feature to send notification in case that the execution of job requires a shorter duration than expected.

 Requirements:

  • The Job configuration contains the warn_if_shorter_than setting.  

  • ./config/factory.ini configuration file:

    • mail_queue_only=true

    • mail_queue_dir setting specifies a directory to store the JobScheduler mails

    • mail_on_warning=true

 TaskIfShorterThan supports the following attributes:

AttributeUsageDescription
scheduler_idOptional

Notifications are restricted to the JobScheduler instance with the given identification. By default notifications will be sent for all JobScheduler instances that log into the same database.

Regular expression can be used.

notifications

 

Optional

Integer

Specifies the number of transfers the same notification to a System Monitor.

Default: 1


SystemMonitorNotification / Timer 

...

Code Block
languagexml
titleExample (order job)
collapsetrue
<?xml version="1.0" encoding="ISO-8859-1"?> 
<job  title="Sample Job with Store Result Monitor" order="yes" stop_on_error="no" tasks="1">     
  <params>
     <!--
     set the scheduler_notification_result_parameters parameter
     -->         
    <param name="scheduler_notification_result_parameters" value="file_size"/>     
  </params>     
  
  <!--
  calculate and create the new order parameter if necessary
  -->
  <script language="java:javascript"><![CDATA[             
      function spooler_process(){                                  
        var order    = spooler_task.order;                 
        var params   = spooler.create_variable_set();                 
        params.merge(spooler_task.params);                 
        params.merge(order.params);                      
        
        // parameter scheduler_file_path was set in the previous job chain step
        var file     = new java.io.File(params.value("scheduler_file_path"));                 
        var fileSize = file.length()/1024;                 
        order.params.set_var("file_size",fileSize.toString());                          
      return true;             
      }]]>     
   </script>          
 
   <!-- 
   set the StoreResultsJobJSAdapterClass as a monitor
   the StoreResultsJobJSAdapterClass as a monitor
   -->     
   <monitor  name="notification_monitor" ordering="1">         
     	<!-- JobScheduler version 1.9.x, 1.10.x
	<script java_class="com.sos.scheduler.notification.jobs.result.StoreResultsJobJSAdapterClass" language="java"/>
        -->
   
        <!-- JobScheduler version 1.11.x, 1.12.x --> 
    
   <monitor <script namejava_class="notification_monitorcom.sos.jitl.notification.jobs.result.StoreResultsJobJSAdapterClass" orderinglanguage="1java"/> 
   </monitor>

   <run_time  
     	<!-- JobScheduler version 1.9.x, 1.10.x
	<script java_class="com.sos.scheduler.notification.jobs.result.StoreResultsJobJSAdapterClass" language="java"/>
        -->
   
        <!-- JobScheduler version 1.11.x, 1.12.x --> 
        <script java_class="com.sos.jitl.notification.jobs.result.StoreResultsJobJSAdapterClass" language="java"/> 
   </monitor>

   <run_time /> 
</job> 

 

...

Usage

The Message can be configured on the following parent nodes as a CDATA element :

  • SystemMonitorNotification / Notification / NotificationInterface
  • SystemMonitorNotification / Notification / NotificationCommand
  • SystemMonitorNotification / Notification / NotificationMail 
    • Subject
    • Body
  • SystemMonitorNotification / Notification / NotificationJMS / Message

The Message can contain: 

  • Fixed values
  • Variables

...

/> 
</job> 

 

Message
Anchor
message
message

Usage

The Message can be configured on the following parent nodes as a CDATA element :

  • SystemMonitorNotification / Notification / NotificationInterface
  • SystemMonitorNotification / Notification / NotificationCommand
  • SystemMonitorNotification / Notification / NotificationMail 
    • Subject
    • Body
  • SystemMonitorNotification / Notification / NotificationJMS / Message

The Message can contain: 

  • Fixed values
  • Variables

Example: <![CDATA[ scheduler id = ${MON_N_SCHEDULER_ID}  ]]>

Variables

All variables (except OS environment variables) must be defined by using of the

${<variable name>}

syntax.

Note:

  • Syntax for the JobScheduler version 1.10.6 and higher. Syntax for the JobScheduler version 1.10.4, 1.10.5 (see below) is still supported.
  • Syntax for the JobScheduler version 1.10.4, 1.10.5:  {<variable name>}
  • Syntax for the JobScheduler previous versions: %<variable name>%

The order of the substitution the variables values is:

  1. Table variables.
  2. Service variables.
  3. JOC Cockpit variables.
  4. OS environment variables.

Table variables
Expand
titleVariables: table SCHEDULER_MON_NOTIFICATIONS

 Table of the history of steps of processed orders / jobs.

NameDescription  Note
${MON_N_ID}
Unique notification id 
${MON_N_SCHEDULER_ID} 

...

Id

...

Variables

...

of the JobScheduler 
${

...

MON_N_TASK_ID}Id of the JobScheduler task  
${MON_N_STEP} Consecutive number of the order step 
${MON_N_ORDER_HISTORY_ID} Id of the JobScheduler order  
${MON_N_JOB_CHAIN_NAME} Name of the job chain of the order  
${MON_N_JOB_CHAIN_TITLE}Title of the job chain of the order   
${MON_N_ORDER_ID} Unique (within the job chain) id of the order  
${MON_N_ORDER_TITLE} Title of the order  
${MON_N_ORDER_START_TIME} Timestamp of the start of the order

syntax.

Note:

  • Syntax for the JobScheduler version 1.10.6 and higher. Syntax for the JobScheduler version 1.10.4, 1.10.5 (see below) is still supported.
  • Syntax for the JobScheduler version 1.10.4, 1.10.5:  {<variable name>}
  • Syntax for the JobScheduler previous versions: %<variable name>%

The order of the substitution the variables values is:

...

Table variables
Expand
titleVariables: table SCHEDULER_MON_NOTIFICATIONS

 Table of the history of steps of processed orders / jobs.

Unique notification id
NameDescription  Note
${MON_N_ID}
 
${MON_N_ORDER_SCHEDULEREND_IDTIMEId Timestamp of the end of the JobSchedulerorder 
${MON_N_TASKORDER_TIME_IDELAPSED} The time or difference in seconds between a beginning time and an ending time of the orderId of the JobScheduler task  
${MON_N_ORDER_STEP_STATE} Consecutive number State of the order stepinside the job chain 
${MON_N_ORDER_HISTORYSTEP_START_IDTIME} Id Timestamp of the start of the JobScheduler order order step  
${MON_N_ORDER_JOBSTEP_CHAINEND_NAMETIME} Name Timestamp of the job chain end of the order order step  
${MON_N_JOBORDER_STEP_CHAINTIME_TITLEELAPSED}Title of the job chain of the order  The time or difference in seconds between a beginning time and an ending time of the order step  
${MON_N_ORDERJOB_IDNAME} Name Unique (within the job chain) id of the order job  
${MON_N_ORDERJOB_TITLE} Title of Title of the order job 
${MON_N_ORDERTASK_START_TIME} Timestamp of the start of the orderjob task start  
${MON_N_ORDERTASK_END_TIME} Timestamp of the job task end of the order 
${MON_N_ORDERTASK_TIME_ELAPSED} The time or difference in seconds between a beginning time and an ending time of the orderjob task 
${MON_N_ORDER_STEP_STATERECOVERED

0 = dependent of the ${MON_N_ERROR} - ok or error was not recovered,

1 = error was recovered  

State of the order inside the job chain

 
${MON_N_ORDER_STEP_START_TIME}RETURN_CODE}Return code number Timestamp of the start of the order step  
${MON_N_ORDER_STEP_END_TIME} Timestamp of the end of the order step AGENT_URL}JobScheduler Agent uri 

Available with release 1.11.2

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-351

 

${MON_N_ORDERCLUSTER_STEPMEMBER_TIME_ELAPSEDID}The time or difference in seconds between a beginning time and an ending time of the order step  ID of the Scheduler cluster member (only used in cluster mode)

Available with release 1.11.2

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-352

 

${MON_N_JOB_NAME}ERROR}

0 = ok

1 = error 

Name of the job 

 
${MON_N_JOBERROR_TITLECODE} Title of Exception-code of the job error  
${MON_N_TASKERROR_START_TIMETEXT}Timestamp Exception message of the job task start (that processed the order)  
${MON_N_TASK_END_TIMECREATEDTimestamp of the job task endnotification initial record  
${MON_N_TASK_TIME_ELAPSEDMODIFIED} The time or difference in seconds between a beginning time and an ending time of the job task Timestamp of the latest changes to this notification record  

 

HISTORY_ID}, job_chain = ${MON_N_
RETURN
JOB_CHAIN_
CODE}
NAME}(${MON_N_
AGENT
ORDER_
URL}
ID}), error = ${MON_N_
CLUSTER
ERROR_
MEMBER_ID
TEXT}
Code Block
languagexml
titleExample
collapsetrue
 scheduler id = ${MON_N_SCHEDULER_
RECOVERED} 0 = dependent of the
ID}, history id = ${MON_N_ORDER_
ERROR} - ok or error was not recovered,

1 = error was recovered  

 Return code number  JobScheduler Agent uri 

available with release 1.11.2

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-351

Expand
titleVariables: table SCHEDULER_MON_SYSNOTIFICATIONS

 Table of the history of notifications sent to a system monitor.

 JITL-352NERROR}

0 = ok

1 = error NERRORCODE Exception-code of the job error 
NameDescriptionNote
${MON_SN_ID}Unique system notification id  ID of the Scheduler cluster member (only used in cluster mode)

available with release 1.11.2

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
key
${MON_SN_NOTIFICATION_ID}

Reference to the SCHEDULER_MON_NOTIFICATIONS.ID  table

 
${MON_SN_CHECK_ID}

Reference to the SCHEDULER_MON_CHECKS.ID   table

 
${MON_NSN_ERRORSYSTEM_TEXTID} Exception message of the job (that processed the order) 

Reference to the element attribute

SystemMonitorNotification / @system_id

defined in the XML configuration file

 
${MON_SN_NSERVICE_CREATEDNAME} 

Reference to one of both element attributes

  • SystemMonitorNotification / Notification / NotificationMonitor / @service_name_on_error
  • SystemMonitorNotification / Notification / NotificationMonitor / @service_name_on_success

defined in the XML configuration file 

Timestamp of the notification initial record 

 
${MON_SN_
N
OBJECT_
MODIFIED}
Timestamp of the latest changes to this notification record  

 

Code Block
languagexml
titleExample
collapsetrue
 scheduler id = ${MON_N_SCHEDULER_ID}, history id = ${MON_N_ORDER_HISTORY_ID}, job_chain = ${MON_N_JOB_CHAIN_NAME}(${MON_N_ORDER_ID}), error = ${MON_N_ERROR_TEXT}
TYPE}

NotificationObject type

  • 0
    • JobChain
  • 1
    • Job
  • 10
    • TaskIfLongerThan
  • 11
    • TaskIfShorterThan
  • 12
    • TaskWarning
  • 20
    • MasterMessage
  • 100
    • dummy code for interlal using 
  • 10,11,12,20
    • Available with release 1.12.9
      • Jira
        serverSOS JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId6dc67751-9d67-34cd-985b-194a8cdc9602
        keyJITL-522
      • Jira
        serverSOS JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId6dc67751-9d67-34cd-985b-194a8cdc9602
        keyJS-1837
${MON_SN_OBJECT_TYPE_NAME}
See ${MON_SN_OBJECT_TYPE} above.
  • JobChain
  • Job
  • TaskIfLongerThan
  • TaskIfShorterThan
  • TaskWarning
  • MasterMessage
Available with release 1.12.9

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-522

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJS-1837

${MON_SN_TITLE}
Titel
  • Job, JobChain
    • empty
  • MasterMessage, TaskWarning, TaskIfLongerThan, TaskIfShorterThan
    • E-Mail subject generated by the JobScheduler Master
Available with release 1.12.9

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJITL-522

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJS-1837

Expand
titleVariables: table SCHEDULER_MON_SYSNOTIFICATIONS

 Table of the history of notifications sent to a system monitor.

NameDescription
${MON_SN_ID}Unique system notification id 
${MON_SN_NOTIFICATION_ID}

Reference to the SCHEDULER_MON_NOTIFICATIONS.ID  table

${MON_SN_CHECK_ID}

Reference to the SCHEDULER_MON_CHECKS.ID   table

${MON_SN_SYSTEM_ID} 

Reference to the element attribute

SystemMonitorNotification / @system_id

defined in the XML configuration file

${MON_SN_SERVICE_NAME}

Reference to one of both element attributes

  • SystemMonitorNotification / Notification / NotificationMonitor / @service_name_on_error
  • SystemMonitorNotification / Notification / NotificationMonitor / @service_name_on_success

defined in the XML configuration file 

${MON_SN_OBJECT_TYPE}

NotificationObject type

  0 = JobChain

  1 = Job

100 = dummy code for interlal using 

${MON_SN_RETURN_CODE_FROM} 

Reference to the element attribute

SystemMonitorNotification / Notification / NotificationObjects / JobChain / @return_code_from

defined in the XML configuration file

 
${MON_SN_RETURN_CODE_TO}

Reference to the element attribute

SystemMonitorNotification / Notification / NotificationObjects / JobChain / @return_code_to

defined in the XML configuration file 

 
${MON_SN_STEP_FROM}

Reference to the element attribute

SystemMonitorNotification / Notification / NotificationObjects / JobChain / @step_from

defined in the XML configuration file 

 
${MON_SN_STEP_TO}

Reference to the element attribute

SystemMonitorNotification / Notification / NotificationObjects / JobChain / @step_to

defined in the XML configuration file 

 
${MON_SN_STEP_FROM_START_TIME}Timestamp for the start of the order step  
${MON_SN_STEP_TO_END_TIME}Timestamp for the end of the order step   
${MON_SN_STEP_TIME_ELAPSED} The elapsed time or the difference in seconds between the start and end times of the order step   
${MON_SN_NOTIFICATIONS}

Reference to element attribute

SystemMonitorNotification / Notification / NotificationObjects / JobChain / @notifications

defined in the XML configuration file  

 
${MON_SN_CURRENT_NOTIFICATION}Number of notifications that already sent to a System Monitor 
${MON_SN_MAX_NOTIFICATIONS}

0 = notifications counter was not reached

1 = notifications counter was reached, all configured notifications were sent

 
${MON_SN_ACKNOWLEDGED}

0 = not acknowledged

1 = acknowledged 

 
${MON_SN_RECOVERED}

0 = recovery not sent

1 = recovery sent

 
${MON_SN_SUCCESS}

0 = Notification onError, SystemMonitorNotification / Notification / NotificationMonitor / @service_name_on_error

1 = Notification onSuccess, SystemMonitorNotification / Notification / NotificationMonitor / @service_name_on_success

 
${MON_SN_CREATED}Timestamp of the initial system notification record   
${MON_SN_MODIFIED}Timestamp of the latest changes to this system notification record   
Code Block
languagexml
titleExample
collapsetrue
 step from = ${MON_SN_STEP_FROM}, step to = ${MON_SN_STEP_TO}, notification = ${MON_SN_CURRENT_NOTIFICATION} (of ${MON_SN_NOTIFICATIONS})

...