What information it keeps
The scope covers the information exported by these sources. Direct reception of FlexxAgent logs or telemetry is not part of this feature. Execution outputs that are already part of an operation are included in its history.
How it works
- Initial import. Retrieves the history that is still available in the SaaS and shows from which date coverage exists for each source.
- Nightly synchronization. Downloads pending records and their details by date intervals. Keeps the events and versions received, incorporates updates to records already imported and reviews open operations.
- Confirmation and recovery. Confirms each batch once its data is saved. If a download is interrupted, it resumes the work without duplicating records and shows incomplete intervals.
- Local query. Updates searches and daily summaries. The full detail is loaded when each record is opened.
The archive reflects the last completed synchronization. With a daily run it may lag by about one day, plus the processing time. A failure can extend that interval.
Deployment and configuration
The synchronizer, the query service and the repository are deployed on a VM with persistent, expandable storage. In higher-load installations, the application and the database can be hosted on separate servers.Deployment requirements
- Connectivity and credentials. Outbound HTTPS connection from the component to the FlexxClient API and a technical identity of the organization with the necessary read permissions.
- Access. Access to the local interface from the authorized network and authentication for users who query or administer the archive.
- Storage. SSD or equivalent low-latency storage, with free space for the import, indexes and maintenance.
- Backups. An independent backup destination and a recovery policy defined by the organization.
Main settings
Querying the history
The views let you filter by dates and identifiers and, depending on the record, by actor, device, action, status, flow or microservice. Results are paginated and large exports are processed in the background. Each view shows the covered period and the last successful synchronization. The history remains queryable during a SaaS outage if the local component and the configured authentication services are working.Retention and protection
Retention is configured in months or years:- Audit. The period is counted from the event.
- Operations. The period is counted from the closing or the last change, whichever is later. Open operations are kept.
Indicative sizing
Sizing depends on daily operations, the size of their related data, audit, retention and concurrent queries. The number of devices helps describe a scenario, but it is the actual activity that determines the resources.Assumptions of the examples
- Activity and retention. Five new operations per device per day and five years of retention, calculated as 1,825 days. This is a planning assumption, not an average product usage figure.
- Unit of calculation. One operation corresponds to one record in the Operations history. An action on several devices can produce many associated results.
- Size per operation. Approximately 22.6 kB of physical storage per operation, including events, associated details and indexes. Replace this value with the measurement from your organization’s local archive.
- Queries. Paginated queries, daily summaries and between five and ten concurrent query users. Resources are validated through a test with representative data.
The data column includes operations and their associated details. Audit, additional versions and the engine’s operating space must be measured separately. The initial SSD includes a planning reserve whose sufficiency must be checked when adding those items.
The operating system disk, backups and replicas require additional capacity. For 250,000 daily operations or more, the CPU and RAM distribution and the separation of services are defined through specific sizing.
In the 50,000 daily operations scenario, 91.25 million operations are kept over five years. The reference configuration is 8 vCPU, 64 GB of RAM and 4 TB of expandable usable storage, subject to validation with the actual load.
Adjust capacity to your organization
- Measure activity. Use a representative period of two to four weeks. Record the operations and bytes archived each day, including results, audit and new versions. Include days with high activity.
- Project retention. Multiply the measured daily growth by the retention days and by the expected activity growth. Include indexes and the engine’s operating space without counting items already measured twice.
- Reserve capacity. Divide the expected total by 0.70 to keep 30% free space. Size backups and replicas independently.
- Validate performance. Check searches and the opening of old records while an import is running. Confirm that the download finishes within the agreed window and adjust CPU, RAM, disk or concurrency if necessary.