Installing/Updating Sisense Logging Helm Chart

Last updated: October 21, 2026

Tier Deployment
Enterprise On-Prem

Sisense offers its users the logging feature, which is an app that collects all logs from all Sisense pods, and saves them in the node’s file system under /var/log/sisense, providing you an alternate easy access to Sisense logs.

The Logging Helm chart (logging-monitoring) deploys the following components in the Sisense namespace:

  • A fluent-bit DaemonSet, which reads the container logs on every node and forwards them to the aggregator.

  • A fluent-bit-aggregator Deployment, which receives the logs and writes them into log files under /var/log/sisense on the node where it runs.

  • A cronjob-logrotate CronJob, which rotates and compresses the log files every 15 minutes on the same node.

The log files are written to:

  • /var/log/sisense/<namespace>/combined.log - all the Sisense logs

  • /var/log/sisense/<namespace>/<container name>.log - one file per container

  • /var/log/sisense/kube-system/combined.log - the logs of the kube-system namespace

This topic details how to install or update the Sisense Logging Helm chart. If you install Sisense with sisense.sh, the installer installs the Logging chart for you when internal_monitoring: true is set in the configuration file.

Note:

Install it under the same Kubernetes namespace where you install the Sisense app.

Prerequisites

  • You must first install Sisense before installing the Logging Helm chart. The Logging chart reads its settings from a ConfigMap that the Sisense chart creates in the Sisense namespace.

  • kubectl and helm access to the cluster with cluster-admin rights. The chart creates a ClusterRole and a ClusterRoleBinding so that Fluent Bit can read pod and namespace metadata.

  • The Sisense namespace must allow privileged pods and hostPath volumes: Fluent Bit runs as root and reads the container logs from the node, and the logrotate job runs as a privileged container.

Note:

The Logging chart cannot be installed if you are Installing Sisense without ClusterVisibility with namespace-scoped permissions only, because it creates cluster-scoped resources. The sisense.sh installer also skips the Logging chart when cluster_visibility: false is set, and on OpenShift.

Adding the Helm Repo and Searching for the Helm Chart

  1. If needed, add the Sisense Helm repo, and run a quick update to sync with the remote repo:

    Copy 
    helm repo add sisense-fusion https://data.sisense.com/linux/helm/charts/fusion
    helm repo update

  2. Search for the available chart versions with one of the following commands. Use the chart version that matches your Sisense version (for example, 2026.4.0).

Copy 
# Only official versions
helm search repo sisense-fusion/logging-monitoring --versions

# Including non-official/development/customized versions
helm search repo sisense-fusion/logging-monitoring --versions --devel

First Installation

Values Configuration

  1. Download the relevant values file into your server:

  2. Edit the values. The parameters below must be set as follows:

    • sisense_version: <Sisense version> (Example: 2026.4.0). This value is added to every log record.

    • k8s_node_1: <Your k8s node name> (Example: mynode1). The Kubernetes node name, as shown by kubectl get nodes. The aggregator and the logrotate job run on this node, so this is the node where the log files are written.

    • private_ip and public_ip: <Node name or address> (Example: mynode1). These values are added to every log record.

    • kubernetes_cloud_provider: aws, azure, or gke on Amazon EKS, Azure AKS, or Google GKE. Leave it empty on other clusters. Fluent Bit uses this value to select the container log format. On GKE, also set fluentbit.gke.enabled: true.

    • cluster_mode.enabled: false for Single-node, true for Multi-node or cloud. With false, Fluent Bit keeps its buffer on the node under /opt/fluent-bit/storage.

    • If you pull images from a private registry, set repository to your registry, and list your image pull secret names under pullSecrets.

    • Only for Multi-node/Cloud:

      The node label keys in the fluentbit.affinity section are written for a Sisense namespace named sisense (for example, node-sisense-Application). If Sisense is installed in a different namespace, replace sisense in these keys with your namespace.

      Examples:

      Copy 
      # Only for Multinode or Cloud
      # Replace "sisense" in the keys below with your Sisense namespace
      fluentbit:
        affinity:
          nodeAffinity:
            requiredDuringSchedulingIgnoredDuringExecution:
              nodeSelectorTerms:
                - matchExpressions:
                  - key: node-sisense-Application
                    operator: In
                    values:
                    - "true"
                - matchExpressions:
                  - key: node-sisense-Query
                    operator: In
                    values:
                    - "true"
                - matchExpressions:
                  - key: node-sisense-Build
                    operator: In
                    values:
                    - "true"

Installation

  1. After you have completed the pre-configuration above, install the Logging app using the following command:

    Copy 
    # Set your values file name, examples below:
    LOGMON_VALUES=logmon-values-single.yaml
    # LOGMON_VALUES=logmon-values-multi.yaml

    # It must be installed in the same namespace as the Sisense app
    NAMESPACE=sisense

    # Chart version, matching your Sisense version
    SISENSE_SEMVER=2026.4.0

    helm upgrade --install logmon-${NAMESPACE} sisense-fusion/logging-monitoring \
      --namespace ${NAMESPACE} --version ${SISENSE_SEMVER} -f ${LOGMON_VALUES}

  2. Make sure that the Fluent Bit pods are running:

    Copy 
    kubectl -n ${NAMESPACE} get pods | grep fluent-bit

Upgrading Logging

Upgrade the Logging chart after you upgrade Sisense, using the logmon-values file from your previous installation.

Note:

Older versions of the sample values files contained fluentd and global.securityContext sections. The current chart does not use them (logs are aggregated by Fluent Bit), and you can delete them from your file.

  1. In your values file, change the value of sisense_version: to the new Sisense version.

  2. Upgrade the release. Always pass your complete values file, and do not use --reuse-values.

    Copy 
    # Set your values file name, examples below:
    LOGMON_VALUES=logmon-values-single.yaml
    # LOGMON_VALUES=logmon-values-multi.yaml

    # The namespace of the Sisense app
    NAMESPACE=sisense

    # Chart version, matching the new Sisense version
    SISENSE_SEMVER=2026.4.0

    helm upgrade logmon-${NAMESPACE} sisense-fusion/logging-monitoring \
      --namespace ${NAMESPACE} --version ${SISENSE_SEMVER} -f ${LOGMON_VALUES}