Console logs and log file path

[raphaelzoellner]

Behavior

The logging configurations log_file and console_output seem to have no effect. https://github.com/gbseuropagmbh/iqsuite-sasi/blob/sasidaemon-1.0.0/charts/sasi-daemon/values.yaml#L222-L233

      [CONFIG]

      # Path and name of the SASI daemon log file
      log_file                            = /opt/sasidaemon/datadir/lased.log

      # If true, logging is done on the console, otherwise the log file is used.
      # Possible values: true, false. Default: false
      console_output                      = false

• Setting the path for log_file does not result in a log file created at the path. The log file seems to be located under /opt/sasidaemon/datadir/log/ for any configuration.
• Setting console_output to true does not result in logs being written to STDOUT or STDERR.

Expected Behavior

• Setting the path for log_file results in a log file being created and logged to at the specified path.
• Setting console_output to true results in logs being written to STDOUT and STDERR.

[gbseuropagmbh]

Both logging configurations have an effect if the iqsuite-sasi service is successfully connected to the iQ.Suite. Please check whether the connection to iQ.Suite is established.

[raphaelzoellner]

Thanks for clarifying, the connection from iQ.Suite to the SASI Daemon could indeed not be successfully established.

We suspect this is the case since only the starter-port (25317) of the SASI Daemon is exposed via the ingress https://github.com/gbseuropagmbh/iqsuite-sasi/blob/main/charts/sasi-daemon/templates/ingress.yaml#L48

and http instead of https seems to be used by iQ.Suite to establish the connection.

Failed to get daemon status from http://{redacted}:443

To configure the SASI Daemon Connection in iQ.Suite we can configure the following parameters:

• Daemon Host
• Daemon Port
• Starter Port

Therefore we suspect that the Daemon Port must be exposed to iQ.Suite (e.g. via an Ingress) as well, is this the case? We also suspect that the same hostname is used for the connection to both ports. Typically either different Hostnames are used by Ingresses or non colliding Path Prefixes to route the traffic to the different ports. Are there such non-colliding path prefixes for the Daemon Port and Starter Port that could be used to expose both Daemon and Starter Port under the same Hostname and Port to iQ.Suite?

Is there any way to configure iQ.Suite to use https for the connection to the daemon and starter ports?