Network Interaction of System Components
- Network Interaction of System Components
- Interaction Between the Monitoring Agent and the Operavix Application Server
- Data Volume and Composition
- Port
- Protocol
- Interaction Between the Operavix Application Server and ClickHouse DBMS
- Data Volume and Composition
- Port
- Protocol
- Interaction Between Users and the System Web Interface
- Data Volume and Composition
- Port
- Protocol
Interaction Between the Monitoring Agent and the Operavix Application Server
Data Volume and Composition
The monitoring agent requests configuration settings from the application server every 30 minutes. The exchange format is JSON. The data volume is up to 100 KB.
If automatic monitoring agent updates are enabled, the agent checks for updates every hour. If updates are available, the agent downloads and installs them. The average size of update files is 30 MB.
While a monitored employee is working on their computer, a ZIP archive of up to 5 KB containing activity data is sent every 10 minutes. If the connection to the server is lost, the agent stores the generated archives and sends all unsent data when the connection is restored.
In the event of an agent crash, a dump is generated and later sent to the server. The size of the transmitted dump is up to 10 MB.
It is recommended to ensure a connection speed of at least 256 Kbit/s between the user's workstation (where the monitoring agent is installed) and the application server.
Port
By default, the agent establishes an outgoing connection to the application web server on port 8010/TCP. The port used by the web server can be changed in the application configuration files.
Protocol
All communication occurs over the HTTPS protocol. Configuration is available via the configuration file.
Interaction Between the Operavix Application Server and ClickHouse DBMS
Data Volume and Composition
- The application server continuously transmits data collected by monitoring agents, as well as system metadata, to the ClickHouse DBMS
- The application server loads processed data from ClickHouse required for report generation and system operation
- The volume of data exchanged between the application server and ClickHouse depends on multiple factors (number of monitored employees, report complexity, user activity level, etc.). It is recommended to ensure a connection speed of at least 10 Mbit/s between these system components
Port
By default, the application server establishes an outgoing connection to the ClickHouse DBMS server on port 8123/TCP.
Protocol
All communication occurs over HTTPS (HTTP if no SSL certificate is installed on the ClickHouse server).
Operavix initiates the connection.
The following encryption protocols are used:
- TLSv1.2:
- ciphers:
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp256r1)
- TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (secp256r1)
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (secp256r1)
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1)
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp256r1)
- ciphers:
Interaction Between Users and the System Web Interface
Data Volume and Composition
Users interact with the system through the web interface using a browser. It is recommended to ensure a connection speed of at least 256 Kbit/s between the user's workstation and the Operavix application server.
Port
By default, the user's workstation establishes an outgoing connection to the application web server on port 8010/TCP.
Protocol
All communication occurs over HTTPS (HTTP if no SSL certificate is installed on the application server).
Was the article helpful?