System Operation

Operation of the Data Storage Subsystem

Database access is protected at the file system level. To view the built-in file-based database, you must use a dedicated utility.

The connection between the Operavix application server and the ClickHouse database is established over HTTPS. If internet access is available, the Docker image is automatically downloaded from the remote server. In case of limited internet access, the image is provided separately.

Operation of the User Activity Monitoring Module

The User Activity Monitoring Module (UAMM) operates independently of the server. It receives only the necessary configuration settings. If the server is unavailable, the UAMM stores all user data locally until the server becomes available again.

Authentication between the system (server side) and the UAMM is based on mutual authentication via API keys. An API key is created for the connection between the system and the UAMM. For each API key, a set of privileges is defined, which determines access rights within the system, and an authentication method is selected. The specialized Monitoring Agent privilege is used for connecting to the UAMM.

Available authentication methods:

• Via Active Directory
• Using SSL certificates

Mutual authentication via AD involves client authentication on the server using client-side Active Directory. Mutual authentication via SSL certificates involves client authentication on the server through a certificate that ensures secure interaction between the server and other systems.

The monitoring agent uses mutual authentication via AD.

Platform and Analytics Modules

The Platform and Analytics modules are the core components of the system and are used for system configuration and business process analysis. A web browser is required to work with these modules. The modules perform the following functions:

1. System Configuration:
   • Configuring general system parameters
   • Setting up connection to ClickHouse
   • Monitoring configuration
   • Activity filter configuration
   • API key configuration
   • Security settings
   • Project access configuration
2. Viewing and Configuring Company Information:
   • Viewing and editing employee data
   • Viewing and configuring the role model
   • Integration configuration
3. Creating Data Marts and Building Analytical Reports:
   • Uploading external tables
   • Uploading tables obtained through system integrations via the Automation module
   • Additional data processing using SQL scripts
   • Building analytical reports

All security objects are logged within the modules. To work with the system, users must be authorized and have an assigned access role with system access enabled. The modules are configured by the system administrator.