Configuring one-time job settings for proactive problem management
As a problem coordinator, you can configure and run one-time clustering jobs for proactive problem management. You can create a maximum of three jobs.
When you set up a one-time clustering job, the algorithm runs once to cluster incidents based on the selected criteria.
By default, a maximum of 200000 incidents are considered while creating a one-time Proactive problem management job. However, you can increase the limit by customization.
To create a one-time job
- On the Proactive problem management settings page, click Create one-time job.
- In the General section, enter a job name.
- Select the language for the incident text processing. Even though your incident text contains mixed language, pre-processing is done on the basis of the selected language.
In the Data Set section select the fields on which you want to create clusters.
To also view the required system fields, select the Show system fields check box. The system fields cannot be removed. Except for Submitter, all other system fields cannot be removed. Some fields may be hidden from the data set by your admin to comply with privacy regulations.Tip
The fields that appear in BMC Helix ITSM display their field labels, system names (in brackets), and often display their additional description (in English only) in the data set. Therefore, when you choose amongst similar fields in the data set for creating clusters, we recommend you select the field that displays its label, system name and description. For example, while choosing between CI and CI(HPD_CI), we recommend you select CI(HPD_CI) because it displays the CI label, HPD_CI system name and its description as
.- You can apply filters on the fields to further refine your data set.
Click the required filter category and select one of the following options:
Option
Description
Equals to
Select this option to include values in the filter.
Not equals to
Select this option to exclude values from the filter.
- Search and select the field value that you want to include or exclude.
Click Apply filters.
In the Data range section, specify the date range that the job should use to search incident data. The Data range date field is the date field that is used to search for incidents within the defined data range.
- In the Create clusters section, specify the parameters by which the data is to be grouped.
- For the first level of grouping, select from one of the data fields. If you select Machine learning, you cannot select the second level grouping.
- For the second level of groupings, you can select Machine learning or another set of data fields (excluding the data field already selected in level 1 grouping).
If you have selected Machine learning, you can specify the text fields to be clustered, but Summary is the default text field that is used.
In the Advanced machine learning section, the Let the system set the number of clusters check box is selected by default.
You can upload custom stop words in the form of .txt file where each stop word is defined on a new line. Stop words are commonly used words that are ignored when the text is processed.
Every time you upload a new file containing the updated stop words, it overrides the old file.
BMC Helix ITSM Insights has a built-in library of stop words for every supported language. The algorithm refers to the library and your preferred stop words while processing incident information.- Click Run now.
The job configuration is saved. A job might take several minutes to complete, depending on the incident data to be processed. Refresh the jobs table to check if the job is completed.
When the job run is completed, the jobs table displays job status in the Jobs table. If the job run was not successful, the Job message column displays the reason why the job failed. Once the job is successfully run, you can select it from the Jobs list in the dashboard to view the clusters.
To edit a recurrent job
To edit a recurrent job, click the edit icon in the Actions column. Make the necessary changes to the job.
The changes you have done will take effect in the next job run.
To delete a recurrent job
To delete a recurrent job, click the delete icon in the Actions column. When you delete a job, the job definitions, that is, the data fields and filters applied are also deleted. Also, all job runs associated with that job are deleted.