Linux-Supported CLI Commands for Sisense

This page provides a list of commands and log locations that you can use to debug your Sisense deployment on Linux, as well as ways to optimize Containerd Storage in RKE2 deployments, check status of the nodes, pv/pvc, helm history, and more (see Using Sisense CLI Commands).

Get kubectl tab completions:
source <(kubectl completion bash) 2>/dev/null

Get helm tab completions:
source <(helm completion bash) 2>/dev/null

Get a list of pods:
kubectl -n sisense get pods
OR
kubectl -n sisense get pods -o wide

Access management logs:
kubectl -n sisense logs $(kubectl -n sisense get pods -l app="management" -o custom-columns=":.metadata.name" )

Tail the log and print the last 10 lines:
kubectl -n sisense -f --tail=10 logs $(kubectl -n sisense get pods -l app="management" -o custom-columns=":.metadata.name" )

Disable colors in logs:
kubectl -n sisense set env deployment/management DISABLE_COLORS_LOG=true

Get Kubernetes events:
kubectl -n sisense get events

Monitor Kubernetes events:
kubectl -n sisense get events --watch

Restart and build the Sisense service:

kubectl -n sisense delete pod $(kubectl -n sisense get pods -l app="build" -o custom-columns=":.metadata.name" )

Restart all services:
kubectl -n sisense delete pods $(kubectl -n sisense get pods -o custom-columns=":.metadata.name")

The location of log directories:
On the first installed node:

• /var/log/sisense/namespace/
• /var/log/sisense/sisense/combined.log -- logs of all services

For each service, there is a log file that you can retrieve, for example:

• /var/log/sisense/sisense/query.log
• /var/log/sisense/sisense/api-gateway.log

Get Sisense CLI:
To access the Sisense CLI: see "Accessing the Sisense CLI" in Using Sisense CLI Commands.

Add the add_completion-sisense.sh file to the home directory:
source add_completion-sisense.sh

Get a list of ElasticCubes from the CLI:
si elasticubes list

Build an ElastiCube from the Sisense CLI:
si elasticubes build -name ariel -type full

View disk usage for shared storage:
kubectl -n sisense exec -it $(kubectl -n sisense get pods -l app="management" -o custom-columns=":.metadata.name" ) -- bash -c "df -H /opt/sisense/storage"

Get all services:
kubectl get services -n sisense

Execute bash on a pod:
kubectl -n sisense exec -it $(kubectl -n sisense get pods -l app="management" -o custom-columns=":.metadata.name") bash

List all blocked devices in the system:
lsblk

Get Kubernetes dashboard URL:
kubectl cluster-info

Get an Admin user token:
kubectl describe secret -n kube-system admin-user-token

List helm releases:
helm list --all

Kill all evicted pods:
kubectl get po --all-namespaces | grep Evicted | awk '{print $2, "--namespace", $1}' | xargs kubectl delete pod

Get the Grafana of the cluster:
kubectl -n monitoring get svc prom-operator-grafana

 

Check nodes details (status, scheduled pods, events, resources pressure, etc.):

kubectl get nodes

kubectl describe nodes

 

Check PV and PVC details:

kubectl get pv

kubectl get pvc

kubectl describe pv

kubectl describe pvc

 

Check installed Helm charts and deployment history of each:

helm ls -A

helm history -n <namespace> <chart_name>

 

Clean exited containers and unused images to release the storage (for on-prem deployments with RKE2 i.e. starting from L2025.2):

1. Navigate to the rke2 directory:

   cd /var/lib/rancher/rke2/

2. Copy the ‘crictl’ binary to the path recognizable by your $PATH variable. In this example, it is /usr/local/bin :

   sudo cp bin/crictl /usr/local/bin/

3. Copy the config file, which is necessary for binary execution in the /etc directory:

   Sudo cp agent/etc/crictl.yaml /etc/

4. After performing the steps above, you will be able to execute the ‘crictl’ command directly. Execute the following two commands to 1) Remove all stopped (exited) containers and print the result, and 2) Remove all unused container images and print the result:

   sudo crictl ps -a --state Exited -q| xargs -r sudo crictl rm | wc -l

   sudo crictl rmi --prune | wc -l