Versions Compared

Key

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

...

  • MonitoredObject/JobChains can contain several JobChain definitions for monitoring of error or success conditions
  • MonitoredObject/JobChains/JobChain has the following attributes
    • scheduler_id (optional) - JobScheduler instance with the given identification. By default - JobChain will be checked in all JobScheduler instances that logged into the same database
    • name (optional) - Job chain name including possible folder names. By default - all JobChains for defined scheduler_id are checked
    • step_from (optional) - Start Job node name for checking
    • step_to (optional) - End Job node name for checking
  • MonitoredObject/Timers can contain several Timers definitions for performance measurement
  • MonitoredObject/Timers/Timer has the following elements
    • MonitoredObject/Timers/Timer/JobChains (optional) - can contain several JobChain definitions for performance measurement
    • MonitoredObject/Timers/Timer/JobChains/JobChain has the following attributes
      • scheduler_id (optional) - JobScheduler instance with the given identification. By default - JobChain will be checked in all JobScheduler instances that logged into the same database
      • name (optional) - Job chain name including possible folder names. By default - all JobChains for defined scheduler_id are checked
      • step_from (optional) - Start Job node name for checking
      • step_to (optional) - End Job node name for checking
Code Block
languagehtml/xml
  <?xml version="1.0" encoding="utf-8"?>
  <CheckHistoryConfiguration>
  ....
  
               <Timers>
                   <Timer>
		   <!-- 
                    configure job chains and maximum execution time for performance measurement
                
                    impact: if the execution of job chain samples/sample_jobChain_1 is greater as calculated time (in seconds),
                    the order will be set as performance problem.
                
                    The calculation uses the order parameter FILE_SIZE.
                
                    Parameter FILE_SIZE must be configured for storing in the database.
                   -->
                       <JobChains>
		          <JobChain name="samples/sample_jobChain_1"/>
		       </JobChains>
                       <Maximum>
                       
                           <Script language="javascript"><![CDATA[
                              function calculate()\{
                                   var fileSize		       = new java.lang.Double(%FILE_SIZE%);
                                   var timerExpiryFactor       = 0.0025;
                                   var timerExpiryTolerance    = timerExpiryFactor*0.1;
                                   var timerExpiry 	       = new java.lang.Double(timerExpiryFactor+timerExpiryTolerance);
                                   timerExpiry 		       = timerExpiry*fileSize*60;
                              return timerExpiry;
                              \} 
                              calculate();
                              ]]></Script>
                        </Maximum>
		    </Timer>
		</Timers>
     ...     
  </CheckHistoryConfiguration>

...