Useful helm commands [Linux]
How to check Helm charts with “heml” commands. Applies to all on-prem Sisense for Linux versions.
Step-by-Step Guide:
Check when each Sisense version was installed, if there were issues with the chart installation, the status will be “failed”:
helm history -n sisense sisense
REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION
1 Fri Feb 14 14:58:35 2025 superseded sisense-2025.1.0280 L2025.1.0.280 Install complete
2 Wed Apr 2 03:32:29 2025 superseded sisense-2025.1.0595 L2025.1.0.595 Upgrade complete
3 Tue Apr 29 03:10:29 2025 superseded sisense-2025.2.0212 L2025.2.0.212 Upgrade complete
4 Tue Jun 24 07:06:21 2025 deployed sisense-2025.2.0469 L2025.2.0.469 Upgrade complete
In the same way you can check releases in other namespaces, you can press “TAB, TAB” to see available charts:
helm history -n monitoring
cloud-logs (fluent-bit-0.49.1 -> deployed)
sisense-prom-operator (kube-prometheus-stack-2025.2.0469 -> deployed)
Or use the following command to see all available charts in all namespaces:
helm ls -A
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
cloud-logs monitoring 4 2025-06-24 07:21:12.795986349 +0000 UTC deployed fluent-bit-0.49.1 4.0.3
sisense-prom-operator monitoring 7 2025-06-24 07:06:02.441821773 +0000 UTC deployed kube-prometheus-stack-2025.2.0469 v0.81.0
logmon-sisense sisense 1 2025-06-26 00:09:10.234398513 +0000 UTC deployed logging-monitoring-2025.2.0496 1.0
prov-sisense sisense 34 2025-06-26 00:07:44.008380591 +0000 UTC deployed provisioner-2025.2.0496 L2025.2.0.496
psmdb-operator sisense 1 2025-04-15 09:11:32.809178656 +0000 UTC deployed psmdb-operator-1.19.0 1.19.0
sisense sisense 1 2025-06-26 00:08:22.949225233 +0000 UTC deployed sisense-2025.2.0496 L2025.2.0.496
Conclusion:
With the help of the “helm” command, you can check Sisense and other charts for any issues and additional information
References/Related Content
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.
