Insight Discovery Collector does not move the Agent's XMLs using filecopy

Summary

Customers may have a large number of Discovery Agents installed on their devices (Windows OS)

Agents directly copy the scan result files to another system, ie, a Discovery Collector share directory where it may upload the result into Cloud.

Due to a bug JSDCLOUD-10648 - Discovery Import does not queue up jobs to execute - will return a 400 Bad Request there could be a limitation on how many scan results could be imported at the same time.

Let’s say a customer has 500 Agents, a separate file (one from each laptop) will be sent to a Collector.
In a given time, the collector will contain more than one Scan result which may result to an error described in the bug (it may depend on how large is the Scan Zip directory)

Prior to Insight Discovery v.3.0.0 - the Collector would have split the collected data into two zip files: one with the Hosts results, one with Discovery Settings, and adding an XML File to include the Collector information.

However, a Collector, regardless the version (2.29 or 3.1) does not move the Agent's XMLs using filecopy, so there is not a way to split the collected data into one single big file, which may lead to a failed import into Cloud due to JSDCLOUD-10648

Expected Results

• Improve Collector functionality to gather and split Agents results into one single file

Actual Results

• In Collector v2.29, it does not move Agents XML results, and discovery results are split into one with the Hosts results, one with Discovery Settings.
  
  

• In Collector v3.30 does not move Agents XML results, and the collector moves the Zipped file as they are, and never adds a Collector XML
  • JSDSERVER-11101 - Insight Discovery Collector objects are no longer created