...
MonitoredObject/JobChains
can contain severalJobChain
definitions for monitoring of error or success conditionsMonitoredObject/JobChains/JobChain
has the following attributesscheduler_id
(optional) - JobScheduler instance with the given identification. By default - JobChain will be checked in all JobScheduler instances that logged into the same databasename
(optional) - Job chain name including possible folder names. By default - all JobChains for defined scheduler_id are checkedstep_from
(optional) - Start Job node name for checkingstep_to
(optional) - End Job node name for checking
MonitoredObject/Timers
can contain severalTimers
definitions for performance measurementMonitoredObject/Timers/Timer
has the following elementsJobChains
(optional) - can contain severalJobChain
definitions for performance measurementJobChain
has the following attributesscheduler_id
(optional) - JobScheduler instance with the given identification. By default - JobChain will be checked in all JobScheduler instances that logged into the same databasename
(optional) - Job chain name including possible folder names. By default - all JobChains for defined scheduler_id are checkedstep_from
(optional) - Start Job node name for checkingstep_to
(optional) - End Job node name for checking
Minimum
(optional) - expected minimum execution time for all configured job chains in the MonitoredObject/Timers/Timer/JobChainsScript
(optional) - sets the minimum value and has the following attributeslanguage
(optional) - script engine. currently javascript engine will be supported
Maximum
(optional) - expected maximum execution time for all configured job chains in the MonitoredObject/Timers/Timer/JobChainsScript
(optional) - sets the maximum value and has the following attributeslanguage
(optional) - script engine. currently javascript engine will be supported
Sample Timer configuration using order parameter to calculate expected execution time
Code Block | ||
---|---|---|
| ||
<?xml version="1.0" encoding="utf-8"?> <CheckHistoryConfiguration> .... <Timer> <Timers><!-- configure job chains and maximum <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[ execution time for performance measurement impact: if the execution of job chain samples/sample_jobChain_1 is greater as calculated functiontime calculate(in seconds)\{, the order will be set as performance problem. varThe fileSize calculation uses the order = new java.lang.Double(%FILE_SIZE%);parameter FILE_SIZE. Parameter FILE_SIZE must be configured for storing in the database. --> var timerExpiryFactor <JobChains> = 0.0025; <JobChain name="samples/sample_jobChain_1"/> </JobChains> <Maximum> var timerExpiryTolerance <Script = timerExpiryFactor*0.1;language="javascript"><![CDATA[ function calculate()\{ var timerExpiry fileSize = new java.lang.Double(timerExpiryFactor+timerExpiryTolerance%FILE_SIZE%); var timerExpiryFactor = 0.0025; timerExpiry = timerExpiry*fileSize*60; var timerExpiryTolerance = timerExpiryFactor*0.1; var return timerExpiry; = new java.lang.Double(timerExpiryFactor+timerExpiryTolerance); \} timerExpiry = timerExpiry*fileSize*60; return calculate()timerExpiry; \} ]]></Script>calculate(); ]]></Script> </Maximum> </Timer> </Timers> ... </CheckHistoryConfiguration> |
Schema: SystemMonitorNotification_v1.0.xsd
...