Configuring the job parameters and schedule for using Problem Solver
As a problem coordinator, you must create and schedule jobs to generate problem candidate clusters in the Console in BMC Helix ITSM. The Problem Solver job configuration page displays existing jobs and their additional details, such as the applicable company, ticket type, and creation time.
The following image represents the jobs that appear on the Problem Solver job configuration page after you create them:
<INSERT SCREENSHOT>
You can filter and export jobs, and hide columns in the job table based on requirements.
Before you begin
You must have the Problem Config, Problem Master, or Problem User permission to configure and schedule jobs.
To create a job
- On the Problem Solver console, click Manage configuration.
- On the Problem Solver job configuration page, select Configuration > Incident.
The Create incident configuration panel is displayed. - In the General section, enter the following details:
- Enter the name of the job that you want to create.
- Select the company for which you want to create the job.
- In the Data set section, enter the following details:
- Select the incident data fields that the job must consider for clustering.
<insert screenshot of fields> <WHICH FIELDS ARE SELECTED BY DEFAULT> - (Optional) Select the Show fields required by the system checkbox to view the system fields that are hidden by default.
- In Group by (max 3), select up to three incident fields to group the incidents at the first level for clustering.
Only category fields are available for selection, such as service, CI, and company. <WHICH FIELDS ARE SELECTED BY DEFAULT> - In Inputs for machine learning, select the additional field names for matching incidents to be grouped into a cluster.
Only textual fields are available for selection. <WHICH FIELDS ARE SELECTED BY DEFAULT> - (Optional) In Preview of field values, click Show to preview the incident fields that you have selected for clustering.
- Select the incident data fields that the job must consider for clustering.
- In the Schedule section, enter the following details:
- Select the Enable run checkbox to activate the job.
- Select the weekly or monthly recurrence of the job.
<Insert screenshot> - From the Repeat every list, select the day of the week on which the job must run.
- Select the start date and the end date of the recurring job.
- Specify the look-back period.
<insert screenshot>
Lookback time is the period the job considers to when searching for incident data for a job run. For example, a look-back period of 1 month means the job uses 1 month's data up to the day the job is run. You can select the number of days as the lookback period in the job settings. - In Look back date field, select the date that the job considers to search for incidents within the look back time.
- Click Save.
To view and manage existing jobs
- On the Problem Solver console, click Manage configuration.
The Problem Solver job configuration page is displayed. - (Optional) To filter a job, click Filter, and then select the fields based on which you want to filter the jobs.
- (Optional) To export jobs, select the job from the table, and then select one of the following options:
- Export all rows: To export all Data monitoring rules in the table.
- Export selected row: To export the selected Data monitoring rule.
Alternatively, select a rule from the table and click Export all rows.
- (Optional) To hide columns, click Visible columns, and then clear the fields that you want to hide.
Alternatively, select the fields that you want to view in the job table.
Where to go from here
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*