[Linux] Sisense Upgrade Advisor Plugin
Summary: Rafael Trevisan introduces the Sisense Upgrade Advisor, a client-side plugin designed to aid administrators in planning Sisense Linux upgrades by providing a validated, step-by-step upgrade path while adhering to Sisense's rules. The plugin runs within the Sisense administration interface and uses the official documentation as a reference. Key features include a summary of the current environment, a step-by-step upgrade path, and a checklist for upgrade prerequisites. Ido Darnell expresses excitement and plans to test the tool, promising to offer feedback.
Introduction
This article outlines the Sisense Upgrade Advisor, a client-side plugin that helps administrators plan a Sisense Linux upgrade. Given a current version and a target version, it returns a validated, step-by-step upgrade path that respects Sisense's upgrade rules, and it links every step to the official release notes. The plugin runs entirely in the browser, inside the Sisense administration interface. There is no backend service or scheduler to run. It reads the instance's own APIs to detect the current environment, and it keeps the official Sisense documentation as the source of truth.
Upgrade Rules
A Sisense upgrade is often more than a single hop, and the rules that shape the path are spread across the release notes of the versions in between:
Jump limit: No more than three quarterly releases per hop.
MongoDB gates: Each major bump (6 at L2024.2.0.79, 7 at L2025.2.0.235, 8 at L2025.3) has a prerequisite: a build below the threshold reaches a named intermediate build first.
Kubernetes: Each release supports a bounded range, and Kubernetes moves one minor version at a time.
Installer: Provisioning moved from RKE1 to RKE2, with a few environment-specific requirements along the way.
The Advisor encodes each documented gate explicitly so the full path holds together and each step shows its Kubernetes range, installer, and MongoDB version, links to its release notes, and carries any advisory the notes call out, storage changes, ingress migration, or a kernel requirement. Notes appear only when they apply.
Step-by-Step Guide
Prerequisites
A running instance of Sisense (Linux).
Administrator access to the Sisense administration interface.
Installation
Place the sisense-upgrade-advisor folder under File Manager/plugins.
File Manager is located under Admin → App Configuration → File Management.
If File Manager is not available, enable it under Admin → App Configuration → Feature Management → File Management.
Confirm the plugin is enabled under Admin → Add-ons.
Refresh the browser. An "Upgrade Advisor" entry appears in the admin menu, beneath the REST API.
Using the Upgrade Advisor Plugin
Select "Upgrade Advisor" from the admin menu.
The panel opens with a "Detected environment" banner that summarises the running build, Kubernetes version, container runtime, and operating system.
When the running build matches a known release, the Current version is pre-selected for you.
Pick a Current version and a Target version, then click on Calculate Path.
The result is a step-by-step path from the current version to the target.
Each stop shows its build, Kubernetes range, installer, and MongoDB version, links to its release notes, and carries any advisory that applies, for example a MongoDB gate, a feature-compatibility check, a storage or ingress change, or a kernel requirement.
The Requirements tab summarises the Kubernetes compatibility matrix, the operating-system support ranges, and hardware sizing.
The Checklist tab provides an interactive pre-upgrade and post-upgrade checklist.
Alternative access
The Advisor can also be opened directly by URL at;
https://<your-sisense-host>/plugins/sisense-upgrade-advisor/app/index.html
which is handy for bookmarking or sharing a link.
A signed-in Sisense session is required either way.
Download
The plugin is available to download here
Disclaimer
This post describes a custom solution for a specific use case. It may not work in all environments or Sisense versions, so we strongly recommend testing it before deploying to production.
This plugin is not officially supported, maintained, or validated as part of Sisense releases.
If you have questions or need assistance, please leave a comment on this post.
Latest Version that the plugin was tested on : 2026.2.0-build.40
This document describes an advisory tool based on publicly available Sisense documentation. Upgrade paths should always be verified against the official documentation and validated in a non-production environment before production.
Ido Darnell
·Jul 15, 2026 at 4:12 PMThis is phenomenal @Rafael Trevisan I can't wait to test it out! we will add our feedback to this thread