Use > Data Flow Management > Service Discovery > Business Service Discovery > Service Discovery User Interface > Discovery Status - Progress Tab

Discovery Status – Progress Tab

This dialog box displays the progress of running discoveries, and enables you to drill down to discovered CI instances.

To access

Select Data Flow Management > Service Discovery > a node in the tree > Discovery Status pane (on the right) > Progress tab.
Important information The discovery progress information displayed is the last status known by the UCMDB server for each job Trigger CI within the context selected for discovery.
Relevant tasks
See also

Triggered CIs View - Progress/Status Matrix

Displays the status of triggered CIs through the progress of discovery.

UI Element (A-Z) Description
Refresh. Refreshes the matrix.

Add CI. Opens the Choose CIs to Add dialog box, enabling you to add a newly-discovered CI to the triggered CI list. For details, see Choose CIs to Add Dialog Box.

Available: Discovery Modules/Jobs view only, when you select a module/job.
Rerun Discovery. Enables you to rerun the selected discovery modules/jobs.
/

Pause / Resume. Enables you to pause or resume the selected discovery

Note

  • When you pause an active job:

    • triggers that are currently running continue to run until they are finished
    • all the execution information is retained, including errors

  • Jobs are paused based on their defined job execution policies. For details, see Job Execution Policies.

Available: Discovery Modules/Jobs view only
Progress bar

Displays the percentage of new trigger CIs that have completed the discovery process for the set of jobs contained within the focus area that you have selected for discovery since the last time the activity was modified.

Note When you activate discovery, the trigger CIs list are prepared. During this time, discovery progress may not be reflected immediately.

Thereafter, discovery progress is automatically refreshed every 30 seconds.

During the discovery process, you may receive the following message: The progress status does not reflect the latest changes, since the activity is waiting for some of its triggers to rerun.

When you see this message, although the progress bar shows 100% completion, the discovery of the service is not yet complete. After a few seconds, some of the triggers will be rerun. These triggers require a rerun because after they were executed, new information was discovered, possibly causing them to have more results than they did before. This most often occurs for dependency search jobs. Only after the bar shows 100% and this message no longer appears is the discovery is truly finished.

Understanding the Progress/Status Matrix and the Progress Bar

Progress Status Total
Pending Probe Displays the total number of trigger CIs waiting for the Probe to pick them up for execution. Displays the number of triggered CIs successfully waiting for the Probe to pick them up for execution. -- --
Reached Probe Displays the total number of triggered CIs that reached the Probe, and may have started running. Displays the number of triggered CIs that successfully reached the Probe, and may have started running. Displays the number of triggered CIs that successfully reached the Probe and have started running, but have warnings. --
Completed Displays the total number of triggered CIs that completed running (successfully or unsuccessfully). Displays the number of triggered CIs that successfully completed running. Displays the number of triggered CIs that successfully completed running, but have warnings. Displays the number of triggered CIs that failed to complete running, did not reach the Probe, or were not picked up by the Probe for execution.
Total Displays the total number of triggered CIs. Displays the total number of successful triggered CIs. Displays the total number of triggered CIs that were successful, but had warnings Displays the total number of failed triggered CIs.

CI Count View

Clicking a link in the Triggered CIs view enables you to view the number of triggered CIs for each discovery job that have reached the selected stage of discovery and with the selected status.

Important Information In the Discovery Modules/Jobs view, the CI Count job is displayed only when standing on a module which contains 2 or more jobs. If there is only one job in the module, clicking the triggered CI displays the CI Instances view.

User interface elements are described below (unlabeled elements are shown in angle brackets):

UI Element (A-Z) Description
Up one level. Enables you to go back to the Triggered CIs view.
Show triggered CIs. Enables you to drill down to individual triggered CIs.
Refresh. Refreshes the table.

Remove CI. Deletes the selected CI. The CI is deleted from the specific job or activity job.

Available: Discovery Modules/Jobs view only, when you select a module category and select a job.
Rerun Discovery. Enables you to rerun the selected discovery jobs. The execution complies to the defined execution policy for the relevant discovery jobs.
/

Pause / Resume. Enables you to pause/resume a selected job.

Note

  • When you pause an active job:

    • triggers that are currently running continue to run until they are finished
    • all the execution information is retained, including errors

  • Jobs are paused based on their defined job execution policies. For details, see Job Execution Policies.

Available: Discovery Modules/Jobs view only
CI Count Displays the number of triggered CI per job that have reached the selected stage of discovery and with the selected status.
Job Name Displays the list of jobs that have reached the selected stage of discovery and with the selected status.

CI Instances View

Clicking a job in the CI Count view displays the triggered CIs for that discovery job.

UI Element (A-Z) Description
Up one level. Enables you to move up a level of information.
Refresh. Refreshes the list of triggered CIs.

Add CI. Opens the Choose CIs to Add dialog box, enabling you to add a newly-discovered CI to the triggered CI list. For details, see Choose CIs to Add Dialog Box.

Available: Discovery Modules/Jobs view only

Remove CI. Deletes the selected CI. The CI is deleted from the specific job or activity job.

Available: Discovery Modules/Jobs view only

Filter CIs. Enables you to filter the displayed CIs.

  • By Status. Available only when viewing the CIs of a particular discovery job in the Discovery Module/Jobs view.

    • All. Displays all the Trigger CIs.

    • Waiting for Probe. Displays the Trigger CIs that are ready to be dispatched and are waiting for the Probe to retrieve them.

    • In Progress. Displays the Trigger CIs that are active and are running on the Probe.

    • In progress (being removed). Displays the Trigger CIs that are being removed from the Trigger CIs list.

    • Success, Failed, Warning. Displays only those CIs that have the selected status.

  • By Probe. Displays only the CIs triggered by a selected probe/cluster. Click to open the Select Probes dialog box.

  • By Dispatch Type. Displays a list of CIs according to one of the following options:

    • All. Displays both CIs that are used to manually activate the job and Discovery TQL queries that are used to automatically activate the job.

    • Manually Added. Displays the CIs that are used to manually activate the job.

    • By Discovery Query. Displays the CIs that are used to automatically activate the job.

  • Reset. Click to remove any filters.
Show Message. When there are warnings/errors,opens a message box containing all the warning/error messages for the triggered CI.
Show additional data. Opens the Discovered CIs dialog box, enabling you to view additional information about the CI. For details, see Discovered/Created/Last Updated CIs Dialog Box.

Show results for triggered CI. An ad hoc request is sent to the Data Flow Probe and retrieves the latest results of the job (CIT name and number of discovered CIs) that is running on a specific trigger CI.

This ad hoc request does not run the job, but brings the results of the previous job run that are stored in the Probe's database. If the job has not yet run for this trigger CI, a message is displayed. See Show Results for Triggered CI Dialog Box.

If no communication log exists on the Probe, a message is displayed. You can choose to always create communication logs. For details, see Adapter Configuration Tab.

Rerun Discovery. Enables you to rerun the discovery on the selected CI.
/

Pause / Resume. Enables you to pause/resume a selected discovery.

Note

  • When you pause an active job:

    • triggers that are currently running continue to run until they are finished
    • all the execution information is retained, including errors

  • Jobs are paused based on their defined job execution policies. For details, see Job Execution Policies.

Available: Discovery Modules/Jobs view only
Look for To search for a specific Probe, related host, or related IP, enter part of its name in the box and click the button.
<CI Instances table> Displays all the CI instances discovered by selected job. You can drill down into any CI instance. If triggered CIs failed, or succeeded with warnings, you can drill down further to better understand the cause for the warning or failure.
<right-click menu>

In addition to some of the functionality described above, right-clicking a CI enables you to do the following:

  • Debug. Enables you to debug a CI. You can:

    • View the Communication Log

    • Go directly to the job's adapter

    • Go directly to the job's details (Discovery Modules/Jobs view only)

    • Select a script to edit

    • Rerun discovery

      • Enable Communication Log.Creates a log file for this session. The log file contains information about the connection between the Probe and a remote machine.

        Note To capture results about the connection, see the Enable Communication Log And Record Results option in this menu.

      • Enable Communication Log And Record Results. Creates a log file for this session. The log file contains information about the connection between the Probe and a remote machine. Additionally, it enables capturing the discovered results; these discovered results may help in investigating various discovery problems.
      • Enable Scanner Debug Log. Used for most scanner debugging purposes.
      • Enable Scanner Trace Log. Used for more comprehensive scanner debugging purposes.

      Note Communication log files are created on the Probe Manager under the C:\UCMDB\DataFlowProbe\runtime\communicationLog folder. For details on how the communication logs work, see Record DFM Code.

  • Download Scanner Log. Saves the debug or trace log to a specified location.

    If a log for the selected CI is unavailable, enable the debug or trace log using the Rerun Discovery menu option.

  • Run from step.

    Enables you to manually run the job on the selected CI from a particular step in the job's workflow. This is useful if you do not want to rerun the whole discovery job on the CI, but only a part of it.

    Note  

    • The workflow steps are defined in the job’s adapter file. You can view or edit the workflow in the Adapter Definition tab for the relevant adapter. For details, see Adapter Definition Tab.

    • You cannot run the job from particular step if the status of the CI is Waiting for probe or In Progress.

    Available: In the Discovery Modules/Jobs view; For CIs that trigger workflow-based jobs

  • Reprocess Scan File. Reprocesses the scan files of the selected CI.

    Available: In the Discovery Modules/Jobs view; For CIs that trigger workflow-based jobs

Send Help Center feedback