In the left-side navigation pane of the console, choose Custom Monitoring > Jobs to go to the Instance List page.
The following table lists the status of monitoring jobs:
|New||Indicates that the job is newly created. You can click Start for a job in this status.|
|Running||Indicates that the job is running. You can click Stop or Pause for a job in this status.|
|Stopped||Indicates that the job is already stopped. You can click Start for a job in this status.|
|Pause||Indicates that Pause is clicked for this job. You can click Resume or Stop for a job in this status.|
The following figure shows how the status changes.
The operations that you can perform on monitoring jobs include Start, Stop, Pause, Resume, Delete, Duplicate, and Export Template.
The Pause and Stop operations are different:
The Pause operation disconnects the computing engine from the channel. If you click Resume, the connection is set up again, and monitoring of the consumption data continues from the previous consumption position.
The Stop operation destroys the channel.
A job in the Running or Pause status cannot be deleted. A job in the New or Stopped status can be deleted.
When a job is deleted, the configurations, datasets, reports, and alarms related to this job are also deleted.
Before duplicating a job, you must name the new job.
A complete job contains the configuration of data sources, data cleansing, datasets, and alarms. An exported template contains the configuration of data cleansing (sample logs and cleansing rules) and datasets.
An exported template is in JSON format.
An exception may be thrown when you start, stop, pause, or resume a job. The following table lists the error messages and solutions:
|Successful||The operation is successful.||N/A.|
|Data Source cannot be blank.||Data source is not configured for the current job. For example, no data source type or data source is selected.||Configure the data source.|
|Splitting configuration is blank.||Sample logs do not exist or are not split.||Check and add splitting configuration.|
|Dataset, report, or alarm cannot be blank.||Business logic is not yet configured.||Configure reports, alarms, or datasets for the job.|
|Operation frequency too high||The operation interval is 15 seconds by default.||Try again 15 seconds later.|
|Fields in the dataset must exist in the splitting model.||Fields selected in the dataset are not found in the splitting model.||Check the splitting model or dataset.|
|Resources cannot be allocated.||The system fails to allocate resources for this job.||Contact the administrator.|
|Error||Other causes, such as network or system failures||Contact the administrator.|