> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/infraon-configuration/it-operations/discovery/automatic-discovery.md).

# Automatic Discovery

The Automatic Discovery allows you to configure and initiate discovery for Network, Windows, and SSH-supported devices. The Automatic Discovery process identifies supported devices based on the configured IP address, IP range, or subnet and collects the required device information. You can configure the discovery profile, credentials, filters, monitoring options, and agents before starting the discovery.&#x20;

<figure><img src="https://2706319170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOkWBaqDGJVTArkIQTsj%2Fuploads%2FOa0mKBOsFhyecQN9RXDs%2Fimage.png?alt=media&amp;token=d90ed004-ccc2-433a-8279-920dbb7e1dda" alt=""><figcaption></figcaption></figure>

## **Initiate Automatic Discovery**&#x20;

There are three tabs on the 'Automatic Discovery page.&#x20;

**Discovery Details** | Filters | Schedule&#x20;

### **Discovery Details**

The Discovery Details section provides the discovery profile, device information, credentials, agent details, and data collector details settings.

Discovery Details | **Profile and Discovery Information**

<table data-header-hidden><thead><tr><th width="156" valign="top"></th><th width="165.88885498046875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description / Example</strong></td></tr><tr><td valign="top">Profile Name*</td><td valign="top">Enter a name</td><td valign="top">Enter a name for the Discovery Profile. The profile name helps identify and track the discovery configuration.</td></tr><tr><td valign="top">Data Collector Details</td><td valign="top">Configure details</td><td valign="top"><p>Select the Data Collector to be used for the Automatic discovery process.</p><p>The Data Collector is installed within the customer's network and communicates with the target environment using the configured protocols and credentials.</p><p>It collects the required inventory, availability, and performance information and sends the data to Infraon for monitoring.</p></td></tr><tr><td valign="top">Discovery Options</td><td valign="top">Select an option</td><td valign="top"><p>1.   Discover inventory with availability and performance monitoring. </p><p>2.   Discover only Inventory Information.</p><p>3.   Discover inventory with availability and performance monitoring.</p></td></tr><tr><td valign="top">Discover only Inventory Information</td><td valign="top">Select an option</td><td valign="top">Discovers and collects basic inventory information about the selected devices or resources, such as device details, configuration, and hardware/software information. Availability and performance monitoring are not enabled.</td></tr><tr><td valign="top">Discover inventory with availability monitoring</td><td valign="top">Select an option</td><td valign="top">Discovers inventory information and enables availability monitoring to check whether the device or resource is reachable and operational.</td></tr><tr><td valign="top">Discover inventory with availability and performance monitoring</td><td valign="top">Select an option</td><td valign="top">Discovers inventory information and enables both availability and performance monitoring. IMS checks device availability and collects performance metrics for ongoing monitoring.</td></tr><tr><td valign="top">Provide Profile Details</td><td valign="top">Enter details</td><td valign="top"><p>Add a brief description of the discovery profile.</p><p>Example: For WMI devices, Desktops only.</p></td></tr><tr><td valign="top">IP Address*</td><td valign="top">Enter IP details</td><td valign="top">Enter an IP address, IP range, or subnet to be discovered.</td></tr><tr><td valign="top">Import from CSV</td><td valign="top">Import a file</td><td valign="top">Import a device list from a CSV file. This option is optional.</td></tr><tr><td valign="top">Device Credentials</td><td valign="top">Select a credential</td><td valign="top"><p>Create device credentials before performing Automatic Discovery.</p><p>The credential contains the authentication and connection details IMS needs to communicate with target devices during discovery.</p><p>Select a credential that matches the protocol supported by the target device.</p><p>For Automatic Discovery, the supported protocols are SNMP, WMI, SSH, TELNET, and HTTP. The selected credential establishes connectivity, collects device information, and supports monitoring of the discovered device.</p></td></tr></tbody></table>

> \* Fields are mandatory. &#x20;

{% hint style="info" %}
**Note:** Importing from a CSV file is optional. If you don't want to import CSV, you can click the 'Next' button. &#x20;
{% endhint %}

<figure><img src="https://2706319170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOkWBaqDGJVTArkIQTsj%2Fuploads%2FLp2oELRbWLJw5WCixA5p%2Fimage.png?alt=media&amp;token=4b52c9b2-5aad-49f9-b653-8562f5df11e8" alt=""><figcaption></figcaption></figure>

### **Filters**

The Filters section allows you to control which devices are included or excluded from discovery and which server components are monitored. It contains Device Filters, Server Component Filters, and Port.

Click '**Next**' to add details on '**Filters**.'&#x20;

The Filters section contains four areas:

* Default Filters
* Device Filters
* Server Component Filters
* Port Monitoring

The Filters section is optional. You can click **Next** without configuring any filters.

Filters | **Default Filters**

<table data-header-hidden><thead><tr><th width="136.4444580078125" valign="top"></th><th width="165.00006103515625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description / Example</strong></td></tr><tr><td valign="top">Filter By Ping</td><td valign="top">Enable or disable</td><td valign="top">Filters devices based on their response to a ping check.</td></tr><tr><td valign="top">Ping Monitor</td><td valign="top">Enable or disable</td><td valign="top">Uses ping monitoring to check whether a device is reachable.</td></tr></tbody></table>

Filters | **Device Filters**

<table data-header-hidden><thead><tr><th width="188" valign="top"></th><th width="160.55560302734375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description / Example</strong></td></tr><tr><td valign="top">Device Filters</td><td valign="top">Select a condition</td><td valign="top">Configure conditions to include or exclude devices from discovery.</td></tr><tr><td valign="top">Include Devices / Exclude Devices</td><td valign="top">Select an option</td><td valign="top">Specify whether matching devices should be included in or excluded from discovery.</td></tr><tr><td valign="top">Contains</td><td valign="top">Select an operator</td><td valign="top">When Device Name is selected, choose whether the value should exactly match or contain the specified text.</td></tr><tr><td valign="top">Value</td><td valign="top">Enter a value</td><td valign="top">Enter the value used to identify the devices.</td></tr></tbody></table>

Include Devices/Exclude Devices -> **IP Address/Device Type/Device Name -> Equals/Contains -> Number or Device name**&#x20;

Filters | **Server Component Filters**

<table data-header-hidden><thead><tr><th width="116"></th><th width="193.888916015625"></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong></td><td><strong>Action</strong></td><td><strong>Description / Example</strong></td></tr><tr><td><strong>Process</strong></td><td>Select a process or choose <strong>All</strong></td><td>Filters the server components based on the <strong>Process</strong> being monitored. For example, selecting <strong>All</strong> displays components for all available processes.</td></tr><tr><td><strong>Process Name</strong></td><td>Enter or select a process name</td><td>Filters the results by a specific <strong>process name</strong>. For example, selecting a process name displays monitoring information related to that process.</td></tr><tr><td><strong>Service</strong></td><td>Select a service or choose <strong>All</strong></td><td>Filters the server components based on the <strong>Service</strong> being monitored.</td></tr><tr><td><strong>Service Name</strong></td><td>Enter or select a service name</td><td>Filters the results by a specific <strong>service name</strong>. For example, selecting a service displays monitoring information for that service.</td></tr><tr><td><strong>Server Flavour</strong></td><td>Select one or more server flavors</td><td><p>Filters monitoring results by the server operating system/flavor.</p><p>For example, selecting <strong>Ubu</strong> filters the results to Ubuntu servers.</p></td></tr></tbody></table>

Filters | **Port Monitoring**

<table data-header-hidden><thead><tr><th width="111.55548095703125" valign="top"></th><th width="152.88885498046875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Label</td><td valign="top">Action</td><td valign="top">Description / Example</td></tr><tr><td valign="top">Port</td><td valign="top">Enable or disable</td><td valign="top">Enables monitoring of specific network ports during the discovery process. When enabled, IMS checks the configured ports to verify whether the associated services are reachable and available on the discovered device.</td></tr><tr><td valign="top">Port Monitoring</td><td valign="top">Select or enter the port to monitor</td><td valign="top"><p>Specifies the network port that IMS should monitor for the selected device or service. The selected port is checked during discovery to determine whether the corresponding service is reachable.</p><p></p><p><strong>Example</strong>: Port 80 for HTTP, 443 for HTTPS, or 22 for SSH.</p></td></tr></tbody></table>

{% hint style="info" %}
Note: 'Filters' tab is optional. You can click the 'Next' button without adding details on Filters. &#x20;
{% endhint %}

After adding Device Filters, click '**Next**' to add '**Schedule**.'&#x20;

<figure><img src="https://2706319170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOkWBaqDGJVTArkIQTsj%2Fuploads%2FJIeczN3hg3VwFPpojHy2%2Fimage.png?alt=media&amp;token=5b1382d9-3901-48f5-a432-75856273dc57" alt=""><figcaption></figcaption></figure>

### **Schedule**

The Schedule section determines when Automatic Discovery should start. You can start discovery immediately using Discover Now or configure a Discovery Schedule.

Schedule | **Types**

<table data-header-hidden><thead><tr><th width="161.33331298828125" valign="top"></th><th width="154.88885498046875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description / Example</strong></td></tr><tr><td valign="top"><strong>Discover Now</strong></td><td valign="top">Enable the option</td><td valign="top">Initiates the discovery from the current time. This option is enabled by default when no Discovery Schedule is configured.</td></tr><tr><td valign="top"><strong>Discovery Schedule</strong></td><td valign="top">Configure a schedule</td><td valign="top">Schedule Automatic Discovery to run according to the selected schedule mode and date/time.</td></tr></tbody></table>

#### Discovery Schedule

The Discovery Schedule section lets you specify when discovery should run.

Scheduling Mode | **Basic Details**

<table data-header-hidden><thead><tr><th width="174.66668701171875" valign="top"></th><th width="291" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Scheduling Mode</strong></td><td valign="top"><strong>Purpose</strong></td><td valign="top"><strong>Example Use Case</strong></td></tr><tr><td valign="top">Once</td><td valign="top">Runs Automatic Discovery one time at the specified date and time.</td><td valign="top">Perform an initial discovery when adding a new network range or subnet.</td></tr><tr><td valign="top">Every</td><td valign="top">Runs Automatic Discovery repeatedly at a specified interval.</td><td valign="top">Run discovery every 6 hours to identify newly added or changed devices in a dynamic network.</td></tr><tr><td valign="top">Daily</td><td valign="top">Runs Automatic Discovery once every day at the specified time.</td><td valign="top">Perform daily discovery to identify newly connected devices and update device information.</td></tr><tr><td valign="top">Weekly</td><td valign="top">Runs Automatic Discovery on a selected day of the week and at the specified time.</td><td valign="top">Run discovery every Sunday to periodically identify changes in the network environment.</td></tr><tr><td valign="top">Monthly</td><td valign="top">Runs Automatic Discovery once each month at the specified date and time.</td><td valign="top">Perform monthly discovery to periodically reconcile devices and identify changes in a stable network.</td></tr></tbody></table>

&#x20;Scheduling Fields | **Basic Details**

<table data-header-hidden><thead><tr><th width="165.77777099609375" valign="top"></th><th width="227.55560302734375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description / Example</strong></td></tr><tr><td valign="top">at*</td><td valign="top">Select the date and time when the Discovery should run.</td><td valign="top"><p>This field's availability may vary based on the selected scheduling mode.</p><p></p><p><strong>Example</strong>: 23 September 2026, 11:30 AM</p></td></tr><tr><td valign="top">Summary Message</td><td valign="top">View Summary Message</td><td valign="top"><p>Displays a confirmation summary of the configured Automatic Discovery schedule.</p><p></p><p><strong>Example</strong>: Scheduled on 23 September 2026, 11:30</p></td></tr></tbody></table>

After adding details to the 'Discovery Schedule,' click 'Submit' to initiate the 'Automatic Discovery.'&#x20;

<figure><img src="https://2706319170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOkWBaqDGJVTArkIQTsj%2Fuploads%2FpJNw0B6eOzVSYJYE66Qq%2Fimage.png?alt=media&amp;token=f4a14275-0dab-455b-888a-824ea21ef15c" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
'Discovery Schedule' section is optional. By default, it will enable the 'Discover Now' button. &#x20;
{% endhint %}

&#x20;On Successful discovery, Download Jobs (per device) will be created automatically using the inputs provided on the Discovery Page and from System Default, and the Configurations and operational Data will be downloaded immediately.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infraon.io/infinity/user-guide/infraon-configuration/it-operations/discovery/automatic-discovery.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
