| Table of Contents | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The role of the loader is to take files from a folder and upload them into the dashboard.
...
FolderPath - can be local folder or UCN
ApiKey - See here
UploadApiUrl - BusinessGPT upload service API URL- See here
PerformanceFileCount - Help: After how many files to write into the log, the performance of the total number of files and process time. Default 50.
DBPath - local path to SQLite DB file
RunningIntervalMinutes - the service scans the folder every interval for new files that were added to the folder
ReprocessAllFiles - default False. Set to True to reprocess all the files in the folder and upload them again.
Enable copilot eDiscovery data processing
CopilotDataFolderLocation - the location of the ZIP file from the eDiscovery
Notes: FolderPath must be accessible by the service. The service runs with Network Service account and is authenticated with the computer's credentials to remote servers. So if the FolderPath is a network shared folder, need to give read permissions to the computer on that folder.
...
In next version, the service will update the ContentSourceName in the content info table to be “FileLoader” and the ContentSourceIP to the host's IP from which the service is running.
Measuring performance
The File uploader sends each document to the Firewall API. Once the Firewall API inserts the document into the content list, it returns to the loader to get the next file.
Based on AGAT typical files, it takes around 0.2 sec for a file
So, if you have 10,000 files, it would take around 0.5 hours.
Syncing performance to the dashboard
Every time (based on PrefromanceFileCount ), the service will write the performance into the log the performance.
In next version, it will sync the data into the preference table. https://agatsoftware.atlassian.net/wiki/spaces/SKYP/pages/3184656385/BusinessGPT-+BG+Tables+SRS#TABLE---BG_PERFORMANCE
...
You can see a list of DB tables and run SQL queries like SELECT/UPDATE/etc.
Copilot Auditing
When configured to process copilot- the file uploader can process the results of a manual export of the eDiscovery prompts.
When enabled (EnableCopilotProcessing), the service will look for the files in this location:
“CopilotDataFolderLocation”. Each file is parsed, and the prompt and response are sent to the Firewapp API (the same as the proxy sends the data)
The FileLoader sends the user's API key manually updated in the config file.
If the user is missing, send it to Unknown@company.com.
The parser of CoPilot review sets is used by both the File Uploader and the ingestor
The CopliotReviewSetParser is a DLL that unzips the Review Set and extracts the prompt, responses, users, time, and files.