Scheduling Full Discoveries in "CNO for Visibility"Controlling the Maximum Concurrent Full Discoveries The informers are running periodically a full discovery of the Kubernetes clusters and send the results to the instance. When multiple large clusters are reporting to the instance simultaneously, we may accumulate a large backlog of messages, meaning message processing might be delayed or even aborted if the backlog exceeds some limit. To avoid this situation, the instance controls the execution of full discoveries and limits the number of concurrent full discoveries. The maximum number of concurrent full discoveries is 5 and it is controlled using the system property sn_acc_visibility.max_concurrent_full_discovery. The recommended values range is between 2 to 8. In most cases, there is no need to change the default value. When the time comes to run a full discovery on a given cluster, and the number of current full discoveries is at the limit, the "Full Discovery Status" field on the informer will read "Queued". Once other full discoveries end, the current informer status will change to "In Progress". Informers which are in "Queued" state, will be served in ascending order of their "Next full discovery" time. if the informer status is "Down", the system will not attempt to execute the discovery and will re-schedule the next discovery cycle to be the current time plus 24 hours. Setting the Next Full Discovery Time The informers table has a column, which is not displayed by default, called "Next Full Discovery". To show this column, navigate to the informers list (CNO for Visibility -> Home) and follow the instructions to personalize the list and expose this column. When the informer is first registered on the instance, the "Next Full Discovery" is set to the current time. Once the discovery completes, the "Next Full Discovery" is updated to be the current time plus the full discovery interval, which is 24 hours by default. Users can edit the "Next Full Discovery" time in the informer record and set it to the desired time in the future. Once this time will arrive, the system will first queue and then execute the discovery. Once it is completed, the next cycle will set based on the configured interval. It is also possible to set the "Next Full Discovery" to a past time. In that case, the system will queue the informer for an immediate full discovery.