Discovery Jobs

Prev Next

Overview

Discovery jobs identify devices and resources across your IT environment and collect information to support asset inventory. Each job defines the discovery source, the targets to scan, the credentials to use, and the execution settings. You can run jobs as needed or configure recurring discovery to refresh inventory information.

A Discovery job defines which devices to scan, which methods and credentials to use, how much information to collect, and how the work is executed. Example, the Network job wizard follows five stages: Identity, Scope, Type, Settings, and Schedule. Windows systems use WMI, Linux systems use SSH, and network devices use SNMP. Results can be reviewed at the job, host, and discovered-device levels.

Select the appropriate job type based on the type of device, you want to discover:

Discovery requirement

Job type

Discover Windows computers, Linux systems, routers, switches, or firewalls

Network

Identify virtual machines and resources in public cloud environments

Cloud

Discover Docker containers and Kubernetes resources

Container

Identify guest virtual machines through a virtualization platform

Hypervisor

Inventory instances on supported database platforms

Database

Discover Active Directory structures and objects

Directory

Identify SAN arrays, NAS filers, and Fibre Channel switches

Storage / SAN

A single environment may require several discovery jobs. For example, a virtualized database environment may use Hypervisor discovery to identify guest virtual machines, Network discovery to collect guest operating system inventory, Database discovery to identify database instances, and Storage / SAN discovery to inventory storage infrastructure.

Key benefits

  • Control scan boundaries with single hosts, IP ranges, CIDR subnets, host lists, and exclusions.

  • Use protocol-specific credentials and a defined execution order for mixed environments.

  • Balance collection detail and scan load with collection depth, data scope, timeouts, and request limits.

  • Identify incomplete collection through per-host results, logs, and device coverage scores.

  • Investigate recurring failures and worker or credential issues through Discovery Intelligence.

User personas

Persona

Typical responsibility

Discovery administrator

Creates jobs, selects workers, manages credentials, and maintains job settings.

Implementation engineer

Validates connectivity and a small target set before expanding discovery.

IT asset manager

Reviews discovered devices, data completeness, and asset mapping status.

Support engineer

Investigates failures using run history, host results, logs, and worker health.

Persona responsibilities are suggested operating roles; they do not define application permissions.

Before you begin

Confirm the following with the administrators responsible for your environment before creating or expanding a scan.

  • You can access ITAM and the relevant tenant or department and Discovery pages.

  • The target addresses are correct, authorized for discovery, and reachable from the selected worker.

  • You have suitable WMI, SSH, or SNMP credentials for the intended device types.

  • A worker is available and connected to the network containing the targets.

  • Required protocol services and network access are enabled for the targets.

  • You have agreed on exclusions, collection depth, and an acceptable scan window.

Common use cases

Use case

How to approach it

Validate a new Windows server

Use a Network job with Single Host / IP, WMI credentials, and an immediate test run.

Inventory Linux hosts

Use a Network job with SSH and a defined host list or address range.

Discover routers and switches

Use a Network job with SNMP and credentials appropriate to the devices.

Scan a mixed subnet

Use CIDR Subnet, exclusions, and the applicable WMI, SSH, and SNMP methods.

Audit detailed Windows configuration

Use a small scope and Deep collection, then inspect device coverage.

Maintain inventory freshness

Validate an immediate run, then enable scheduled runs with an agreed interval.

Guide navigation

Read the job type and jobs list sections first, then follow the wizard stages. Use the Windows, Linux, and network device examples to apply the workflow. The remaining sections cover results, operational health, best practices, troubleshooting, and implementation verification.

Field names preserve the visible UI labels. Asterisks in screenshots identify required fields. Example names, addresses, and frequencies in the procedures are illustrative and should be replaced with values approved for your environment.

Understand the Discovery jobs list

Use this page to locate existing jobs and review their latest state before creating another job for the same scope. Click a job name to inspect its details. 

To access Discovery Jobs, perform the following steps:

  1. Click Workspace > ITAM > Asset > Discovery > Discovery Jobs.

  2. The Discovery Jobs list page is displayed as shown in the following figure.

    Figure: Discovery Jobs list page

    Below illustration is further enhanced from the original screenshot to help you with easily identifying usage of various UI elements on the Job list page.

    Figure: Discovery Jobs list page Enhanced with Visual Recommendations

  3. Select the Department from the dropdown on the left for which you want to view the jobs list or create a New Job. 

  4. From the Discovery Jobs page, you can get a glimpse of total jobs, successful jobs, failed jobs as well as Devices discovered or discovered with errors. 

  5. In addition, you can also view the type of job run, method, scope, coverage and last status of the job.

  6. In addition, you can also disable a Job or take Actions on the Job such as: 

    1. Run now: Click Run now, to immediately run the job. Status will change to Running and then to Completed or Failed. 

    2. View runs: Click View runs, to view the details of a particular job in more detail.

      Figure: View Run
      In addition, if you further scroll-down you can view the Scan Results and also view the Logs of the Run. This is particularly useful, when you need to run and identify why a particular job failed to execute using the logs.

    3. Clone Job: In case you want to replicate a particular job, you can use Clone job and specify a name, which will create an exact copy of the current job.

      Figure: Clone Job

    4. Edit Job: Click Edit Job, in case you want to modify an existing job.

Figure: Discovery jobs list

Field or control

Description

Department

Limits the working context to the selected department.

New job

Opens the discovery job type selection page.

Search for

Finds jobs in the displayed list.

Items per page

Controls the number of rows displayed.

Job Name

Identifies the job and opens its details.

Type / Method

Shows the discovery category and configured collection method.

Scope

Summarizes the target definition and number of targets.

Coverage

Shows a coverage indicator for the job. Use job details to interpret host outcomes.

Last Status / Last Run / Duration

Shows the latest execution state, run time, and elapsed duration.

Active

Shows an activation toggle for the job. Validate the operational effect before changing existing jobs.

Actions

Provides row-level action icons. Confirm each icon tooltip before use.

Export / filter / settings icons

Provide list export and display controls.

Summary tiles show counts such as total jobs, active jobs, completed jobs, failed jobs, and discovered devices. A completed job can still include failed or unreachable hosts.