Abstract: Automating discovery server configuration as part of a discovery process includes determining one or more subnets selected from multiple subnets. Each of the one or more subnets selected is associated with a respective scheduled task. In response to determining the one or more subnets selected, one or more available discovery servers are identified from multiple discovery servers. The one or more discovery servers are configured based at least in part on the one or more subnets selected. In response to the automatic configuration, network discovery is initiated to perform the respective scheduled task.

Abstract: Systems and methods for mapping configuration items to business functions within a corporate infrastructure are disclosed. Discovery processes to automatically create and update service maps may introduce an artificial dependency between configuration items that is not necessary to the business function represented in the service map. These unnecessary dependencies may be considered “noise” and unnecessarily complicate the service map. Using machine learning techniques and procedures to identify short lived connections embodiments in accordance with this disclosure, dependency connections that may be considered noise may be detected and flagged. Once detected, these connections may be automatically removed from the service map to improve its accuracy and usefulness. Additionally, a user interface is provided that explains the “reason codes” for identification of noise connections.

Abstract: An example embodiment may involve providing for display a discovery schedule creation page for creating a discovery schedule. The embodiment may also involve, in response to receiving user input indicative of creation of a discovery schedule via the discovery schedule creation page, providing for display a discovery process page. Providing the discovery process page for display may involve, while the discovery process is being carried out according to the discovery schedule, dynamically updating the discovery process page to include total numbers of discovery results. The discovery process page may include selectable links for navigating to and displaying three pages: a discovered configuration items page, an error flow page, and a scheduling summary page.

Abstract: Automating discovery server configuration as part of a discovery process includes determining one or more subnets selected from multiple subnets. Each of the one or more subnets selected is associated with a respective scheduled task. In response to determining the one or more subnets selected, one or more available discovery servers are identified from multiple discovery servers. The one or more discovery servers are configured based at least in part on the one or more subnets selected. In response to the automatic configuration, network discovery is initiated to perform the respective scheduled task.

Abstract: Automating discovery server configuration as part of a discovery process includes determining one or more subnets selected from multiple subnets. Each of the one or more subnets selected is associated with a respective scheduled task. In response to determining the one or more subnets selected, one or more available discovery servers are identified from multiple discovery servers. The one or more discovery servers are configured based at least in part on the one or more subnets selected. In response to the automatic configuration, network discovery is initiated to perform the respective scheduled task.

Abstract: An example embodiment may involve providing for display a discovery schedule creation page for creating a discovery schedule. The embodiment may also involve, in response to receiving user input indicative of creation of a discovery schedule via the discovery schedule creation page, providing for display a discovery process page. Providing the discovery process page for display may involve, while the discovery process is being carried out according to the discovery schedule, dynamically updating the discovery process page to include total numbers of discovery results. The discovery process page may include selectable links for navigating to and displaying three pages: a discovered configuration items page, an error flow page, and a scheduling summary page.

Abstract: An example embodiment may involve providing for display a discovery schedule creation page for creating a discovery schedule. The embodiment may also involve, in response to receiving user input indicative of creation of a discovery schedule via the discovery schedule creation page, providing for display a discovery process page. Providing the discovery process page for display may involve, while the discovery process is being carried out according to the discovery schedule, dynamically updating the discovery process page to include total numbers of discovery results. The discovery process page may include selectable links for navigating to and displaying three pages: a discovered configuration items page, an error flow page, and a scheduling summary page.

Abstract: An example embodiment may involve providing for display a discovery schedule creation page for creating a discovery schedule. The embodiment may also involve, in response to receiving user input indicative of creation of a discovery schedule via the discovery schedule creation page, providing for display a discovery process page. Providing the discovery process page for display may involve, while the discovery process is being carried out according to the discovery schedule, dynamically updating the discovery process page to include total numbers of discovery results. The discovery process page may include selectable links for navigating to and displaying three pages: a discovered configuration items page, an error flow page, and a scheduling summary page.

Abstract: Systems and methods for mapping configuration items to business functions within a corporate infrastructure are disclosed. Discovery processes to automatically create and update service maps may introduce an artificial dependency between configuration items that is not necessary to the business function represented in the service map. These unnecessary dependencies may be considered “noise” and unnecessarily complicate the service map. Using machine learning techniques and procedures to identify short lived connections embodiments in accordance with this disclosure, dependency connections that may be considered noise may be detected and flagged. Once detected, these connections may be automatically removed from the service map to improve its accuracy and usefulness. Additionally, a user interface is provided that explains the “reason codes” for identification of noise connections.

Abstract: Automating discovery server configuration as part of a discovery process includes determining one or more subnets selected from multiple subnets. Each of the one or more subnets selected is associated with a respective scheduled task. In response to determining the one or more subnets selected, one or more available discovery servers are identified from multiple discovery servers. The one or more discovery servers are configured based at least in part on the one or more subnets selected. In response to the automatic configuration, network discovery is initiated to perform the respective scheduled task.