Heex Kernel uses one main configuration file: the Core.conf. It contains several categories:
  • The Core contains several core specific topics such as the connectivity mode or the log level.
  • The TcpServer defines the port used to communicate with your custom implementations.
  • The Orchestrator contains specific topic for the orchestrator.
  • The DataSender and DataUploader contain the collection and upload configurations. You can specify custom behaviour for data collection and uploading.

​
Runtime Configuration

Recognizing that implementations might operate in areas with limited or no connectivity, the Heex Heex Kernel offers several modes to accommodate different connectivity scenarios. The connectivity mode can be changed from the Cloud interface. Here are the available modes:
  • Full Connectivity Mode (default): The Heex Kernel runs expecting good connectivity and shall upload both recording and metadata of any generated event. This is the default mode of operation.
  • Limited Upload Mode: In this mode, only metadata is uploaded, which requires minimal connectivity. This mode is ideal for environments with limited connectivity, yet where real-time event notifications are still desired. Recordings are stored locally for later upload.
  • No Connectivity Mode: The Heex Kernel operates without any connectivity. Events metadata and recordings are stored locally for future upload.