Working with the System

System Service Mode

The Service Mode is used for preparing and conducting maintenance routines, testing, or major system reconfigurations. This mode is also intended for technical maintenance, reconfiguration, and system upgrades. It allows administrators to diagnose incidents or issues arising from system failures or outages.

Enabling or disabling Service Mode is done by editing the configuration file: com.operavix.subsystem.frontend.json, specifically the parameter "service_mode": true or false.

When Service Mode is enabled, users accessing the web interface will see the login form and an informational banner at the top of the page stating: "The system is operating in service mode: scheduled technical maintenance is in progress."

The message displayed to users during Service Mode can be customized in the same configuration file (com.operavix.subsystem.frontend.json) using the parameter "service_mode_message": "Your custom message". The message supports Markdown formatting. For more details about the notification banner and Markdown capabilities, refer to the System Configuration page.

User authentication is only possible if the user’s access role includes the Service Mode privilege set to R (by default, this privilege is granted to the Administrator role).

Users whose access roles do not include the Service Mode privilege will be unable to log in while Service Mode is active. When Service Mode is disabled, the system operates normally and does not check for this privilege during user authentication.

Configuring System Time

System time synchronization occurs between the MMAП (Monitoring Agent) and MNiAO modules. The system time in these modules is based on the time set on the server. The system retrieves the time value in Unix format from the operating system where the server is deployed. The server may be a PC or dedicated hardware running the system. Configuration and adjustment of system time are managed through Windows policies.

Retrieving System Time

To view the current system time, use the GraphQL tool.

Send the following query via the web interface:

{
  server {
    time
  }
}

You will receive a response like:

{
  "data": {
    "server": {
      "time": 1690181560211
    }
  }
}

The time value is in Unix timestamp format. All events are recorded in the security log and database using the server's local time.

Working with Docker Containers

Updating Docker Containers

The Operavix application server and ClickHouse are updated independently. To update the Docker containers (for ClickHouse):

1. Remove the old service:
   # docker service rm operavix-clickhouse
   

2. Deploy the new service:
   # docker service create --name operavix-clickhouse \
   --secret operavix_app_user \
   --secret operavix_app_user_password_hash \
   --secret operavix_clickhouse_dhparam.pem \
   --secret operavix_clickhouse.crt \
   --secret operavix_clickhouse.key \
   --publish published=2222,target=8443,mode=host \
   --mount type=volume,src=operavix-clickhouse,target=/var/lib/clickhouse/ \
   operavix/operavix-clickhouse:{VERSION}
   

   where VERSION is the new Docker container version.
3. Stop the Operavix Windows service.
4. Remove the Docker service: docker service rm operavix-clickhouse.
5. Create and run a new service with the updated ClickHouse version.
6. Restart the Operavix Windows service.