Why do discovery configuration changes (adding/removal/forced discovery) not take effect immediately?
Discovery is a time-intensive process. Messages to the IT Assistant Network Monitoring Service are queued and processed in order. If the network monitoring process is busy discovery a subnet, it might take several minutes before further requests are processed. This might be reflected at the Web-based User interface in the following ways: – If you add a subnet using the Subnet Discovery dialog box, it is not added to the IT Assistant Data Repository until the request is processed. Therefore, opening the Subnet Discovery dialog box again might not immediately reflect the added subnet. – If instrumentation is uninstalled or installed on a system, the data for that system is not updated until the next discovery cycle or until a forced discovery is performed for that system.
Discovery is a time-intensive process. Messages to the IT Assistant network monitoring service are queued and processed in order. If the network monitoring process is busy discovery a subnet, it might take several minutes before further requests are processed. This might be reflected at the browser-based user interface in the following ways: – If you add a discovery range using the Discovery Range dialog box, it is not added to the IT Assistant data repository until the request is processed. Therefore, opening the Discovery Range dialog box again might not immediately reflect the added discovery range. – If instrumentation is uninstalled or installed on a system, the data for that system is not updated until the next discovery cycle or until a forced discovery is performed for that system.
