Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Running discoveries in your network

Running discoveries in your network

You can run discoveries from schedules or scripts to create configuration items, define subnets, or to find resources in AWS and Azure clouds.

MID Server configuration prerequisites

Ensure that your MID Servers are properly configured prior to creating a Discovery schedule.
  • Supported applications: Select the applications that are allowed to use the MID Server. You can use the ALL application option to allow any application to use the MID Server.
  • IP ranges: Define the ranges of IP address the MID Server can scan. To find a MID Server match, the IP range you configure on the Discovery schedule must fall into the ranges that one or more MID Servers can support.
  • Capabilities: Create the capabilities that the MID Server supports. You can use the ALL capability option to allow any application to use the MID Server.

Discovery configuration prerequisites

Ensure that your MID Servers can authenticate on the devices they find and classify configuration items (CI) properly.
  • Credentials: Configure the MID Servers with the login credentials they need to query the devices in the network.
  • Classifications: The device and process classifications provided in the base platform are normally sufficient. Create classifications as needed for the devices, processes, and applications in the network not covered by the default classifiers.

Get started running a discovery

  1. Use the Discovery Configuration Console to get started with Discovery. The console provides configuration options which let you choose the types of devices, applications, and software CIs you want Discovery to find. If you select a CI to exclude from scanning, the instance disables the related probe or classifier that Discovery uses to identify the CI. See Discovery Configuration Console to get started.
  2. Determine what type of discovery to run:
    • Run a Configuration item (CI) discovery to find the devices, computers, and applications on your network. This is the most common type of discovery. Run CI discovery from the Discovery Schedule, where you to set up a recurring schedule or run a discovery on demand. The Discovery Schedule also provides configuration options for MID Servers and the Shazzam port probe.
    • Run a Network discovery to find the internal IP networks within your organization. If you already know the IP address ranges in your network, it is not necessary to run Network Discovery. It is intended for organizations that do not have complete knowledge of the IP addresses available for Discovery in their networks.
    • Run a Cloud discovery to find AWS and Azure resources in your organizations cloud.
    • Run a Serverless discovery to find applications on host machines without the need to discover the host first. Serverless discovery relies on infrastructure patterns to explore CIs on a host. This kind of discovery skips the scanning and classification phases of discovery. You need an advanced knowledge of patterns to use this type of discovery. Refer to Patterns and horizontal discovery to get started with patterns.
  3. After you run a discovery, monitor the results of the discovery and resolve errors if they occurred:
    • Use the Discovery status to see a summary of a Discovery and to access the ECC queue, which shows probe and sensor activity, as well as the actual XML payload that is sent to or from an instance.
    • Use the Discovery dashboard to monitor ongoing Discovery operations.
    • Use the Discovery CI schedule manager to access a report of all discovered devices, see any errors that might have occurred, and view discovery trends. This manager interface shows data for Configuration Item type discoveries.

Updates to site content will be made starting around 4am on January 17th (Pacific Time) and lasting approximately 6 hours.  This site may be intermittently unavailable.