...
Code Block | ||
---|---|---|
| ||
<?xml version="1.0" encoding="utf-8"?> <CheckHistoryConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="CheckHistoryConfiguration_v1.0.xsd"> <MonitoredObject> <JobChains> <JobChain name="samples/sample_jobChain_1"/> <JobChain name="samples/sample_jobChain_2"/> <JobChain name="samples/sample_jobChain_3"/> </JobChains> <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 calculated10 time (in seconds), the order will be set as performance problem. --> The calculation uses the order<JobChains> parameter FILE_SIZE. <JobChain name="samples/sample_jobChain_1"/> </JobChains> Parameter FILE_SIZE must be configured for storing in the database. <Maximum><Script language="javascript"><![CDATA[10]]></Script></Maximum> </Timer> --></Timers> </MonitoredObject> </CheckHistoryConfiguration> |
<!--
Now in order to configure the XML file and following the description from above (about the schema):
- Specify the JobScheduler that should be monitored: Job Scheduler with "MY_JOB_SCHEDULER_ID"
- Specify the JobScheduler objects that should be monitored: Job Chain "MY_JOB_CHAIN_NAME"
- Specify Timer for your JobChain: Timer for Job Chain "MY_JOB_CHAIN_NAME" (moreover a function that calculates the expiration time for the timer)
-->
Explanation
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
Code Block | ||
---|---|---|
| ||
<?xml version="1.0" encoding="utf-8"?> <CheckHistoryConfiguration> .... <JobChains> <JobChain name="samples/sample_jobChain_1"/> </JobChains> <Maximum> <Script language="javascript"><![CDATA[ <Timers> function calculate()\{ <Timer> <!-- configure job varchains fileSize and maximum execution time for performance measurement = new java.lang.Double(%FILE_SIZE%); impact: if varthe timerExpiryFactorexecution of job chain samples/sample_jobChain_1 is greater = 0.0025; as calculated time (in seconds), the order will be set as performance problem. var timerExpiryTolerance = timerExpiryFactor*0.1; The calculation uses the order parameter FILE_SIZE. var timerExpiry = new java.lang.Double(timerExpiryFactor+timerExpiryTolerance); Parameter FILE_SIZE must be configured for storing in the database. timerExpiry = timerExpiry*fileSize*60; --> <JobChains> return timerExpiry; <JobChain name="samples/sample_jobChain_1"/> </JobChains> \} <Maximum> calculate(); ]]></Script><Script language="javascript"><![CDATA[ </Maximum> </Timer> </Timers> function calculate()\{ var fileSize = new java.lang.Double(%FILE_SIZE%); </MonitoredObject> </CheckHistoryConfiguration> |
<!--
Now in order to configure the XML file and following the description from above (about the schema):
- Specify the JobScheduler that should be monitored: Job Scheduler with "MY_JOB_SCHEDULER_ID"
- Specify the JobScheduler objects that should be monitored: Job Chain "MY_JOB_CHAIN_NAME"
- Specify Timer for your JobChain: Timer for Job Chain "MY_JOB_CHAIN_NAME" (moreover a function that calculates the expiration time for the timer)
-->
Explanation
...
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>
|
Schema: SystemMonitorNotification_v1.0.xsd
...