Discovery Worker

Prev Next

The Discovery Worker page is the operational view used to monitor Discovery Worker deployments across customer environments. It shows the machines that host one or more worker instances, the worker status for each host, and the live health of the connection between the host and its workers.

Administrators can quickly see which hosts run Discovery Worker instances, how many workers each host runs, and which workers are Up or Down. The page also shows whether each host can communicate with its workers, helping administrators identify which worker to check when a discovery job fails or appears unavailable.

The page is useful when validating a new deployment, troubleshooting failed discovery jobs, or confirming that worker instances are healthy before scheduling or rerunning discovery jobs.

Key Benefits

  • Monitor host and worker health from a single operational view.

  • Check new Discovery Worker deployments quickly and confirm that expected workers are online.

  • Diagnose failed discovery jobs by isolating affected hosts or worker instances.

  • Improve discovery readiness and reduce delays caused by worker downtime.

Diagram

Use Case

User Persona: Admin

Solution

NovaTech Technologies manages discovery workloads across many locations and departments. Its administrator needs a fast way to confirm worker health, check deployments, and identify issues before jobs fail or inventory activity slows down.

NovaTech admin uses the Discovery Worker page to monitor host and worker health across the environment from one operational view.

How NovaTech uses Discovery Worker?

  1. Monitor host health: Review each host card to confirm which servers are running worker instances and whether the host is currently healthy.

  2. Check deployments: After installation or upgrades, check that the expected number of workers appears and that each worker shows a live and healthy status.

  3. Diagnose failed discovery jobs: When a worker or connection is down, identify the affected host and narrow the problem to a single worker or a broader host issue.

  4. Improve operational readiness: Maintain a consistent view of discovery health so the team can schedule jobs confidently and reduce delays caused by worker downtime.

Access the Discovery Worker page

  1. Navigate to Asset > Discovery > Discovery Worker.

  2. Review the host list shown on the Discovery Worker page. The page opens in a card-based summary view, where each card corresponds to one host machine.
    Figure: Discovery-Worker List Figure: Discovery-Worker List

Discovery Worker view

The top-level view lists the hosts currently running Discovery Worker instances. The summary panel shows the number of hosts and registered worker instances.

Default controls on the page

The following controls appear at the top of the page:

Control

Purpose

Refresh interval

Sets the automatic refresh interval for the host summary. The value selected by default is 5 mins. Other time interval options available in the dropdown are 10,15 and 20 mins.

Showing X hosts · Y workers

Provides a count summary for the number of hosts and worker instances currently displayed.

Search for…

Filters the host list displayed on the page.

Refresh

Reloads the worker status and connectivity data immediately.

Host cards

Represent each host and include summary details such as worker count and Up/Down status.

Host cards and host summary

Each host appears as a card. A host card represents a physical or virtual machine on which administrators have installed one or more Discovery Worker instances.

What a host card shows

A host card shows the host name and a machine icon or indicator, along with the total number of worker instances running on that host. It also summarizes how many workers report Up and how many report Down.

The card can also act as a navigation entry to the host’s detailed network diagram.

Many workers on one host

One of the key behaviors shown in the figure is that a single machine can host more than one Discovery Worker instance.

Each time the Discovery Worker installer runs and creates a new worker, it adds a separate worker service to that host. The platform supports many workers on the same host, and each worker can function independently while belonging to the same machine.

The same machine can host many workers with different identities, and those workers can point to the same application or to different application URLs. Administrators can track each worker’s health separately and review an overall summary for the host.

The host view groups its workers together so administrators can understand the server’s workload without opening each service separately.

View a host network diagram

Selecting a host opens the network connectivity diagram, which shows how the host connects to its associated workers.

This diagram is the most detailed operational view in the page collection. It shows the host and each worker instance in relation to one another and helps identify whether the communication link is healthy or broken.

Diagram layout

The diagram gives a visual overview of the selected host and its Discovery Worker instances. Use the connection lines and status labels to spot workers that are down or disconnected.

Figure: Worker NetworkFigure: Worker Network

The host diagram includes these main elements:

Element

Description

Host node

Shows the host name and IP address. It also includes a summary of the worker count for that host.

Worker nodes

Represent individual Discovery Worker instances. Each worker node includes the worker name, status, and version information when available.

Connection lines

Show whether the host connects to each worker. Live connections use animated lines; disconnected connections use dashed lines.

Host details panel

Displays the host information and worker summary.

Workers on this host

Lists each worker instance tied to the selected host and shows its current status.

Diagram legend

An animated link shows an active connection between the host and worker. A dashed link shows that the worker cannot communicate with the host or that the communication path has failed.

This visual distinction helps administrators detect a running service that cannot communicate with its host or the customer environment.

Host details panel

The right-side details panel in the diagram provides a compact summary of the selected host.

The panel shows the selected machine’s Hostname and IP address, the total number of Workers on the host, and a Status summary of workers that are Up or Down. It also lists the Workers on this host and shows each worker’s status.

The status summary is useful when triaging a discovery issue. For example, if a host has three workers and only one is down, the administrator can identify whether the problem affects only that worker or the whole host.

Worker status definitions

The UI displays workers in a simple health summary. The screenshot shows two main status states: Up and Down.

Status

Meaning

Up

The worker is active, and the assigned host connects to it.

Down

The worker is not healthy or not currently reachable in the host diagram.

Disconnected link

A dashed visual link means the host and worker do not have an active communication path.

In practice, review the worker status and the connection line together. A worker can appear in the diagram but still be effectively unusable if it has lost its connection or its status is down.

Worker version information

Each worker node includes the installed worker version, such as v4.0.0.28 or v4.0.0.9.

This metadata helps administrators confirm which build is running on a host and compare worker versions across environments or worker services on the same machine.

Administrators can use the version to confirm that a host runs the expected build, compare its worker build with another machine, and check whether deployments have drifted across environments.

Example from the figure

The host name is WIN-GKIF104LDV9, its IP address is 1xx.1xx.1xx.1xx, and it has three workers: two Up and one Down.

In the diagram, two workers have live connections, while the third appears disconnected or down.

This is a clear example of how the page separates the host-level summary from the per-worker health view. A host can look healthy overall while one worker remains down or disconnected.

Operational use of the Discovery Worker page

This page is useful for both deployment validation and issue isolation.

Check a deployment

After installing or updating Discovery Worker instances, verify that the page lists the host and shows the expected number of workers. Check that the workers report Up and that the connection lines between the host and workers animate to show live connections.

Use it to diagnose a problem

If a discovery job fails or a worker is unavailable, identify the host that owns the worker, then check whether the host connects to it and whether its status is Up or Down. Compare the other workers on the same host to determine whether the issue affects one worker or more than one.

This makes the Discovery Worker monitoring page a front-line troubleshooting tool before moving deeper into logs, credentials, or network validation.

Best practice

When reviewing any host on this page, check both the host summary and the actual worker connectivity lines. A worker that an administrator installed but that cannot connect is not equivalent to a healthy worker, and a host with one down worker may still be operational for other worker services.

Administrators should treat the page as a health dashboard for the customer environment and use it to triage discovery readiness before scheduling automated jobs.