Arctera™ Insight Capture Configuration Guide
- INTRODUCTION
- DASHBOARD
- IMPORTERS
- File-Based Collector Options
- Amazon S3
- Audio Video
- BlackBerry
- Bloomberg
- Box
- CellTrust
- Chatter
- Chatter Cipher Cloud
- Cisco Webex Teams
- Citrix Workspace & ShareFile
- Dropbox Business
- Dubber Speik Recordings
- Dubber Speik SMS
- EML
- EWS
- Exchange Graph API
- FX Connect
- Google Drive
- IceChat
- JSON
- LSEG (Refinitiv)
- Microsoft Teams
- Microsoft Teams via Webhooks
- NTR-X
- OneDrive for Business
- Pivot
- Redtail Speak
- RingCentral
- ServiceNow
- SharePoint
- Slack eDiscovery
- Symphony
- Text-Delimited
- X (Twitter)
- UBS
- Web Page Capture
- Workplace from Facebook
- XIP
- XSLT/XML
- Verint
- Viva Engage (Yammer)
- Yieldbroker
- YouTube
- Zoom Chat
- Zoom Meetings
- Zoom Meetings Chats
- Zoom Meetings via Archiving API
- MONITORED USERS
- FILTERS
- TARGETS
- SETTINGS
- REPORTS
- APPENDIX
Notes
In the RingCentral collector, data processing also occurs in ranges, however, when a range (chunk) is failed, it is not considered a Data Acquisition Failure։ the information is only logged.
In the Workplace from Facebook and Microsoft Teams via Webhooks collectors, the Data Acquisition Failure report information is generated differently. Specifically, insight Capture messages are generated from the data stream. When a message is not processed for some reasons (e.g., the message contains a new body type, the attachment is missing, or the participant list is absent) the data is stored in the insight Capture DB as a message with the available data (such as from, time, body, subject and more) and the status is specified as Data Acquisition Failure. In this case, the quantity of Data Acquisition Failure messages is equivalent to the number of Unprocessed Messages.
Only the Viva Engage (Yammer) collector has a reprocessing functionality. Before reprocessing occurs, the failed range (chunk) is deleted from DB. When the range fails again, the record is created again and stored in DB.