System Status Monitoring

System Health Check

To monitor the overall health and availability of the system:

• Manual verification: access the system's web interface via the server URL where it is deployed (http(s)://{server_address}:{port}/)
• Automated verification: send a GraphQL query in the following format: {server{status}}

• Log monitoring: track ERROR-level events in the system log file main.log:
  • On Windows: located in C:\ProgramData\Operavix\logs
  • On Linux: located in the container at /var/log/operavix

Recommendations for Integrity Control

To ensure system integrity, it is recommended to monitor the following:

Windows

• File checksums within the C:\Program Files\Operavix directory
• Modifications to configuration files in the C:\ProgramData\Operavix\config directory
• The Operavix file database encryption key file: C:\ProgramData\Operavix\secret_key\secret_key
• The startup command for the Operavix service
• The checksum of the logback.xml file located in: C:\ProgramData\Operavix
• System settings in the Windows Registry key: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Operavix
• The x.509 certificate and private key file — path specified in the C:\ProgramData\Operavix\config\com.operavix.subsystem.frontend.json configuration file
• Security audit log events with object "system" (target@729368) in the C:\ProgramData\Operavix\logs\security.log log file

Linux

• File checksums within the /usr/sbin/operavix directory
• Modifications to configuration files in the /var/lib/operavix/config/ directory
• The Operavix file database encryption key file: /var/lib/operavix/secret_key/secret_key
• The startup command for the Operavix service
• The checksum of the logback.xml file located in: /var/lib/operavix
• The x.509 certificate and private key file — by default, these are located in /run/secrets/operavix_app_https_certificate and /run/secrets/operavix_app_https_certificate_password
• Security audit log events with object "system" (target@729368) in the log file: /var/log/operavix/security.log

In ClickHouse Database

• File checksums within the directory: /usr/bin/clickhouse/
• Directory containing sensitive data: /run/secrets/

Additional Measures for Access Restriction

The following application files and directories may require additional access control measures:

• Working directory:
  • Windows: C:\ProgramData\Operavix
  • Linux: /var/lib/operavix/
  • ClickHouse DB: /var/lib/clickhouse/
• Directory for file-based databases:
  • Windows: C:\ProgramData\Operavix\databases
  • Linux: /var/lib/operavix/databases/
• File-based databases containing critical metadata:
  • Windows: C:\ProgramData\Operavix\databases\main
  • Linux: /var/lib/operavix/databases/main/
• Directory storing logs, including audit logs:
  • Windows: C:\ProgramData\Operavix\logs
  • Linux: /var/log/operavix/
  • ClickHouse DB: /var/log/clickhouse-server/
• Configuration files directory:
  • ClickHouse DB: /etc/clickhouse-server/