You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Each Connector installed as a Content Source in Aspire will create a new Database in MongoDB with its name, and multiple collections that it uses for crawling and serving security information. The following describes what every collection is used for as well as an explanation of each of the fields of the documents stored in them.

What's next?

 

Document Queues and Metadata

  • processQueue

Manages the items that needs to be processed by the workflow, these items may or may not be sent to scanned.

Fields:

Field NameExample

Description

_idC:\test-folder\folderA\testDocument.txtThe unique id of the document
metadata[depends on each connector]The necessary metadata fields the connector needs to fetch or populate this document
type[depends on each connector]The serialized version of the ItemType of the document
statusC, P or A

The document processing status:

C: Completed, means it have been already processed

P: in Progress, means it is currently been processed

A: Available, means it is available for been processed

   
   
   
   

 

  • scanQueue

  • hierarchy

 

Statistics and Logging

  • audit

  • errors

  • statistics

 

Controlling and Incremental

  • status

  • snapshots

 

 

  • No labels