---
title: "Scan nodes"
description: "Scan nodes by hand or on a schedule, and read the results."
product: "Guardian"
edition: "Classic"
type: "overview"
url: "https://docs.cloudhouse.com/guardian/classic/inventory/monitored/scan-options/scan-nodes/"
---
# Scan nodes

By default, Guardian automatically scans all of the nodes within the **Monitored** tab (**Inventory** > **Monitored**) of your instance every day. That means Guardian tracks configuration data and monitors changes on your node(s) over time, allowing for rich configuration differencing. Guardian then stores the total configuration state of every node, making it easy to compare systems and environments, or see how a single system has changed over time.

Applies to: `Guardian Classic`

!!! tip

    During certain integration syncs or bulk add process, you can select the **Automatically start monitoring and scanning newly detected nodes** option to detect and scan nodes every 2 hours. For more information, see [Nodes](https://docs.cloudhouse.com/guardian/classic/getting-started/nodes/index.md).

The following processes assume that you have a Connection Manager or Agent correctly configured for each of the nodes you want to scan. For more information on each of the available scanning methods, see [Guardian Agent](https://docs.cloudhouse.com/guardian/classic/getting-started/agents/index.md)

## Manual scans

Even though Guardian automatically scans nodes every day by default, there are different ways you can trigger a manual scan without having to wait for the next automatic scan to be triggered:

- You can select one or more nodes for scanning from the **Monitored** tab. For more information, see [Node(s) Scan](#node-s-scan).
- You can select individual node groups for scanning from the **Monitored** tab. For more information, see [Node Group Scan](#node-group-scan).
- You can select a node for scanning from the node scan results page within the **Monitored** tab. For more information, see [Node Scan Results Page](#node-scan-results-page).

!!! note

    Alternatively, you can schedule a recurring node scan or configure a node scan that automatically occurs when certain events take place. For more information, see [Job Schedule](#job-schedule) and [Event Actions](#event-actions).

### Node(s) scan

To trigger a manual scan of one or more nodes, complete the following steps:

1. In the Guardian web application, navigate to the **Monitored** tab. By default, all currently monitored nodes are displayed in the 'All Nodes' node group.

    ![Monitored tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/monitored-tab.png)

    !!! note

        If you want to display the list of monitored nodes of a different node group, select a node group from the **Node Groups** drop-down menu.
        ![](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/node-groups-dropdown-menu.png)

2. Select the checkbox of each node you want to scan from the list of options.

    ![Select nodes for scanning](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/select-nodes-for-scanning.png)

3. Click the **Scan X Nodes** button.

The selected nodes are then queued for scanning. Node scans duration vary depending on the complexity of the node, the operating system type, and the network quality between the Guardian appliance and the node itself.

Once complete, the **Node Scan Results** dialog is displayed. Here, you can access information about the nodes, including whether any errors were detected during the scan. To access the task log for the node, click anywhere on the node's row. You can use the information displayed here, or within the task log, to troubleshoot any configuration errors preventing your nodes from being scanned.

![Node scan results](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/node-scan-results.png)

### Node group scan

To trigger a manual scan of a node group, complete the following steps:

1. In the Guardian web application, navigate to the **Monitored** tab. By default, all currently monitored nodes are displayed in the 'All Nodes' node group.

    ![Monitored tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/monitored-tab.png)

2. In the **Node Groups** drop-down menu, locate the node group you want to scan. Then, click the **Settings** button (![Settings button as shown in the Guardian user interface.](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/buttons/settings.png)).

    ![Select node group](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/select-node-group.png)

3. Select **Edit** from the list of options displayed. The node group settings page is displayed.
4. Click the **Scan** button.
    ![Scan button node group](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/scan-button-node-group.png)

The node group is then queued for scanning. Node scans duration vary depending on the complexity of the nodes, the operating system type, and the network quality between the Guardian appliance and the node group itself.

Once complete, the **Node Scan Results** dialog is displayed. Here, you can access information about the nodes, including whether any errors were detected during the scan. To access the test log for each node, click anywhere on the node's row. You can use the information displayed here, or within the test log, to troubleshoot any configuration errors preventing your nodes from being scanned.

![Node group scan results](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/node-group-scan-results.png)

### Node scan results page

To trigger a manual scan from the node scan results page, complete the following steps:

1. In the Guardian web application, navigate to the **Monitored** tab. By default, all currently monitored nodes are displayed in the 'All Nodes' node group.

    ![Monitored tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/monitored-tab.png)

    !!! note

        If you want to display the list of monitored nodes of a different node group, select a node group from the **Node Groups** drop-down menu.
        ![](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/node-groups-dropdown-menu.png)

2. Select the node you want to scan from the list of options. The results of the node's most recent scan is displayed.

    ![Select single node for scanning](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/select-single-node-for-scanning.png)

3. Click the **Scan** button in the top-right corner of the page to trigger a manual scan of the selected node. The **Node Scan** dialog is displayed and the scan is queued for processing.

    ![Scan node button](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/scan-node-button.png)

4. Once complete, an overview of the **Scan Results** is displayed. Guardian compares the results of the current scan with the previous scan to determine whether any changes have occurred on the node in between the two scan dates. If no changes are detected, the following message is displayed, 'No differences were detected!'
5. Click the **View Scan** button to view the results of your scan and close the dialog.

    ![Node scan results page](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/node-scan-results-page.png)

If Guardian detects any changes that occurred between the two scan dates, the following message is displayed: 'Differences detected!'. In this scenario, the following options are displayed:

**View Scan** button
:   Click to view the results of the scan. The results of the previous node scan is updated with the results of the current scan. For more information on each of the sections that are displayed, see [Node Scan Results](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/nodes/node-scan-results/index.md).

**View Diff** button
:   Click to generate a difference report for the current and previous scan of the same node. The node scan results are updated to reflect the configuration items that have been added, removed, and modified between the two scan dates. For more information, see [Scan Differencing](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/configuration-differencing/scan-differencing/index.md).

Additionally, you can click the **Scan** drop-down to display the **With arguments** option. If selected, the **Node Scan Flags** dialog is displayed. Here, you can provide arguments that get passed to the Agent during the scan. This option is not available for website nodes, as they are not scanned using an Agent.

!!! warning

    This is for advanced debugging purposes only and should not be used without first consulting with your support engineer.

![Node scan w arguments](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/node-scan-w-arguments.png)

## Automated scans

Guardian offers different ways you can configure automatic node scans: you can schedule a recurring scan job according to a chosen interval, or you can configure a node scan to start when certain events take place, rather than wait for the next scheduled scan. See below for more information on each of the automated scans available.

### Job Schedule

In the [**Job Schedule**](https://docs.cloudhouse.com/guardian/classic/control/job-schedule/job-schedule/index.md) tab (**Control** > **Job Schedule**), you can schedule a recurring scan job for a node, node group, or environment to run according to a specified schedule. In contrast to a manual scan, a scheduled job enables you to automate the process of scanning your nodes according to a recurring interval. For example, you could configure a node or node group to be scanned every 15 minutes or every 7 days. By setting up a scheduled scan job, you can better track your nodes' configuration differences over time. We recommend setting up a scheduled scan job for all of the nodes within your Guardian instance. For more information on how to add a scheduled scan job, see [Scan – Job Type](https://docs.cloudhouse.com/guardian/classic/control/job-schedule/job-types/scan-job-type/index.md).

![Job schedule tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/job-schedule/job-schedule-tab.png)

### Event actions

Guardian offers the ability to configure actions that automatically occur when certain events take place. You can use this feature to automatically start a node scan. For example, if a specific change is detected within your Guardian instance that may pose a risk for a specific node (or nodes), this action can run a node scan immediately rather than waiting for the next scheduled scan. For more information, see [Action: Perform a Guardian Action](https://docs.cloudhouse.com/guardian/classic/control/events/actions/guardianaction/index.md).

![Guardian action node scan](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/guardian-action-node-scan.png)

## Node scan results analysis

The **Monitored** tab allows you to edit, scan, troubleshoot, and add additional assets for monitoring within their respective areas. Once a scan is complete, click the node you want to analyse the results from the list of options.

![Select node to see results](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/select-node-to-see-results.png)

!!! note

    Nodes on the **Detected** tab (**Inventory** > **Detected**) are not scanned. They must be promoted to the **Monitored** tab, either manually or automatically, for scanning. For more information, see  [Detected Nodes](https://docs.cloudhouse.com/guardian/classic/inventory/detected/detected/index.md).

The node is displayed with the results of the most recent scan. Here, you can select a different scan from the **Scans** drop-down list, compare the selected scan to a previous scan using the **Compare to** drop-down list, or click **Select Node** to select a different node to compare the results of the first scan with. This will generate a difference report for the two nodes to access and compare the complete set of configuration data present on each node, as they occurred on the selected scan dates.

![Scan results](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/scan-results.png)

!!! note

    For more information on the various methods available for configuration differencing, see [Configuration Differencing](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/configuration-differencing/configuration-differencing/index.md).

For example, you could select a scan for node A and compare it to a scan of the same or different date for node B to comparethe differences and similarities between the configuration items of the two nodes. This feature can be critical in uncovering and understanding inconsistencies within your node set. For more information on how to utilise the full scope of functionality available on this page, see [Node Differencing](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/configuration-differencing/node-differencing/index.md).

!!! note

    If the scan is not returning the data you expect, you can access the error report to determine the cause of failure in the [Job History](https://docs.cloudhouse.com/guardian/classic/control/job-history/job-history/index.md) tab (**Control** > **Job History**).

## Scan options

Once a scan is complete, the **Scan** drop-down in the **Monitored** tab allows you to see further scan actions you can take to a node or node group selected. For example, you may view a detailed change report of the scan or export a CSV file with the complete set of scan options applied.

![Scan dropdown list](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/monitored/scan-options/scan-dropdown-list.png)

Here, the following options are displayed.

**View Change Report**
:   Click to generate a detailed change report for the selected node. If selected the **Change Report** tab (**Reports**>**Change Report**) is displayed. Here, you can set a **Time Span** and filter options to customise the output. For more information, see [Change Report](https://docs.cloudhouse.com/guardian/classic/reports/change-report/change-report/index.md).

**Export Node List**
:   Click to export a list of the nodes contained within the selected node group within a CSV file. If selected, the file is downloaded locally to your device.

**Import Scan Options**
:   Click to upload a JSON file containing a list of scan directory options to be added to the node group's settings.

**Export Scan Options**
:   Click to export the complete set of node scan options within a file. If selected, the file is downloaded locally to your device within your format of choice.

**Export Node Scans**
:   Click to export the results of the most recent scan within a ZIP file. If selected, the file is downloaded locally to your device.