Mule Cloud Application Schedule Test
The Scheduler component is a Mule event source that triggers the execution of a flow based on a time-based condition. The scheduler helps to schedule the jobs in a Mule application. A runtime visibility into the schedules in your Mule applications is necessary to identify any long-running schedules. This is because during service updates or security patching CloudHub re triggers any incomplete schedules. To avoid re triggering of any long-running schedules, it is crucial to have an eye on the schedules in the application. Also, the schedules can be triggered more than once which can lead to duplicate data processing. To prevent the data duplication, it is imperative to track whether the schedule has run or not. This test helps administrators to achieve exactly the same.
This test discovers each schedules in every applications on the target environment and reports the status of the schedules, whether it is running or idle. In addition this test also reveals whether the schedules has run, and helps the administrators to identify the exact schedule run time using the detailed diagnosis. This test also helps to identify whether or not he schedule is enabled or disabled. These measures provide the administrators with a deep insight into the schedules of the Mule applications.
Target of the test : A Mule ESB Cloud
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each environment:application:schedule in the target Mule ESB Cloud being monitored.
First-Level Descriptor: Environment
Second-Level Descriptor: Application
Third-Level Descriptor: Schedule
Parameter | Description |
---|---|
Test period |
How often should the test be executed |
Host |
The IP address of the host for which this test is to be configured. |
Port |
The port number at which the specified host listens. |
Username and Password |
By default, the eG agent uses the Cloudhub API version 2 (v2) to collect the metrics from the target Mule ESB Cloud or Cloudhub. To be able to connect to the Cloudhub API v2, the eG agent should be configured with the username and password of a user who is vested with the read only rights. Specify the user and password in the Username and password text boxes. |
Confirm Password |
Confirm the password by retyping it here. |
Organization Name |
To enable the eG agent to monitor a particular organization on Anypoint platform account, specify the name of that organization against this parameter. For instance, org. Doing so will enable the eG agent to monitor each of the components within the specified organization. |
Exclude Environments |
Here, you can provide a comma-separated list of environments that you do not want to monitor. For instance,Sandbox,Design,Production,.... By default this is set as none, indicating that this test will report metrics for all the environments on the target Anypoint platform. |
Exclude Applications |
Here, you can provide a comma-separated list of applications that you do not want to monitor. For instance,Helloworld,AppName,.... By default this is set as none, indicating that this test will report metrics for all the applications on the target Anypoint platform. |
Session Timeout |
Indicate the duration (in minutes) for which this test should wait for a response from the Anypoint Platform. By default, this is set to 60 minutes. This means that any user session that has remained inactive for more than 60 minutes will be automatically logged out from Anypoint platform. You can provide a duration between 15 minutes and 180 minutes in this text box. |
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Status |
Indicates the current status of this schedule on this application. |
|
The values reported by this measure and their numeric equivalents are available in the table below:
Note: This measure reports the Measure Values listed in the table above to indicate the current status of the schedule. However, in the graph, this measure is indicated using the Numeric Values listed in the table above. |
||||||||
Is enabled? |
Indicates whether/not this schedule on this application is enabled. |
|
The values reported by this measure and their numeric equivalents are available in the table below:
Note: This measure reports the Measure Values listed in the table above to indicate whether/not the schedule is enabled. However, in the graph, this measure is indicated using the Numeric Values listed in the table above. |
||||||||
Has run? |
Indicates whether/not this schedule in this application has run. |
|
The values reported by this measure and their numeric equivalents are available in the table below:
Note: This measure reports the Measure Values listed in the table above to indicate whether/not the schedule has run. However, in the graph, this measure is indicated using the Numeric Values listed in the table above. Use the detailed diagnosis of this measure to find out the schedule time. This helps to identify the date and time the Scheduler element last ran. |