Discovery Job Performance

Scheduling Discovery Jobs: There are several factors to consider before activating the discovery jobs. You have to carefully make a decision based on the probe size which depends on the frequency at which you want to run discovery jobs.

	Many Triggers	Less Triggers
Many Probes	Ideal configuration	Wastage of probe resources
Less Probes	Job execution time increase	Ideal configuration

Discovery Jobs - Scheduling

Discovery Scheduler

• Enables the user to define a schedule for a specific job.
• Defines invocation time and frequency of the discovery (daily, monthly)

Time Template

Defines when the job should run.

Invoke on new Trigger CIs immediately

A check mark signifies that the job runs as soon as the Trigger CI reaches the probe. If this column does not contain a check mark, the job runs according to the schedule defined in the Schedule Manager.

Scheduling discovery jobs daily will tax system resources. Identify critical CIs which need to be refreshed and set appropriate aging settings. You can leverage the OOTB blackout schedules to restrict discovery activities during work schedules.

Discovery Jobs - Execution Options

Each job runs with multiple threads.

Max Threads

• You can define a maximum number of threads that can be used concurrently when running a job.
• If you leave the maximum number empty, the probe's default threading value is used (8). The default threading value can be set in the probe’s configuration file.

Max Execution Time

The maximum time allowed for a pattern to run on one Trigger CI. The probe checks for threads that run longer than allowed, and when the number of such threads passes the acceptable amount (set in the properties file), the probe restarts itself.

Adapter Settings

The configurations described on last slide can be set for each discovery pattern in the Pattern Management tab.