Launcher

VisionHub installations are distributed as self-contained folder. A central configuration (based on environment variables) is used to define which components will be started. The launcher uses the pm2 process manager to start and manage configured components.

pm2 collects all relevant component logs in a central folder and provides multiple methods to access these logs locally. The log files do not contain sensitive information (e. g. passwords).

A central monitoring can be setup to collect logs from all VisionHub servers and provide escalation and alerting methods.

The launcher can be started via command line. In this case all sub-processes will be started with this user.

arivis proposes to run the launcher as a service.

Different VisionHub services require full read/write access to a high performace file system. If VisionHub infrastructure is scaled using multiple machines, this file system is required to be mounted on each machine using the SMB or NFS protocol. The launcher provides configuration options to automatically mount a specific UNC path as central data folder. Local UNC mounts as Drive letters will not work when run as a service.

If only read access can be provided for the central file system, a custom configuration allows that the VisionHub components use a secondary file system to store component specific data (full access required).