Sisense Administration | Sisense Community

Community Feedback
Chapters
Events
Forums
Blogs
KB Docs
Support
Learning
Use Case Gallery

Categories

MoreDiscussions

Sisense Administration | Sisense Community

Knowledge Base Docs

Sisense Administration

Created Apr 15, 2026

1 member

89 discussions

Sisense Administration
Cleaning /Opt Storage

Cleaning /opt storage In this article, we'll discuss how we can clean a Linux system of unused files and directories to free up disk space. We’ll see how to carry out the clean-up process manually. We’ll make use of tools such as du and sort. 1. Log in to the Linux server and run df -h . Run cd /opt/sisense/storage && du -sBG * | sort -n For multinode run it from management pod - kubectl -n sisense exec -it management- HASH bash 2. Identify folders with the most size (e.g. data) Run du -sBG farms/* | sort -n Note, in case of Multitenancy feature is enabled, cubes data stored in /opt/sisense/storage/tenants/<tenant_id>/farms folder and the following command should be used: du -sBG /tenants/<tenant_id>/farms | sort -n Check the list of cubes sorted by consumable space: 1G farms/aSampleHealthcare_2022.02.15.08.04.46.779 1G farms/aSampleIAAaECommerce_2022.02.15.10.52.32.376 1G farms/aSampleLeadGeneration_2022.02.15.08.04.47.190 1G farms/aSampleRetail_2022.02.15.08.04.47.614 Once you have reviewed please delete unused cubes and temporary files if any. This article discussed how we can clean up /opt storage of our Linux system. We took a manual approach because it allows us to sort cubes and temporary files by consumable space.
OleksandrPosted 3 years ago • Last reply 2 months ago
1
Sisense Administration
User management [Windows]
Authenticating the Sisense package owner with our Licensing server The password for system activation is auto-generated for each user who signs up on the Sisense website and is received in the welcome email. In case you are not able to log in to the Sisense Activation application with the above credentials, submit a ticket to the Sisense Support Team at https://www.sisense.com/support/ . If you have a Firewall on your machine or in your network, please make sure to activate Sisense accordingly . If you're attempting an offline Sisense Activation, you have an option to get a License Key For Offline Activation By An API Call for the Sisense licensing server. If you are not behind a Firewall, reload Sisense Activation (from the Start Menu), log out, then log back in. After doing so, open your 'Task Manager', choose the 'Services' tab, and restart the service Oxygen. Please note that if you have Malware detection or anti-virus agents running on your machine, they can block the program's authentication service too. We advise disabling these if possible to avoid any doubt. Changing web application password The Web Application user credentials update is done to enable access to the online Sisense platform. Following these simple instructions, you can manage personal user credentials or update them for other users (given Sys Admin role permissions). End users should contact Sys—admin for assistance. If you are a Sys, Admin, Sisense uses a Local Repository database to store all users' credentials for ongoing authentication. Please contact Support to aid with user password change. Resetting your password: Click "Forgot your password? Click here" Enter your email address You will receive the following message Open your mailbox, then click on "Recover Password" Enter new password Changing another user's password (if you are a Sys Admin): Go to 'Admin' tab (1) > 'Users' (2) > Modify user settings (3) Enter password Changing Sys. Admin user details (transferring the role from one user to another): Go to 'Admin' tab > Users > Modify user settings (of Sys. Admin user) > Change the email address If there's a different user already using the Sys. Admin email address you would like to use, change that user's email address to a temporary address, and work on changing the ownership of existing dashboards that are associated with the old user. Related articles: Error: "Your License Has Exceeded Its User Limit" To see your licensing package status, please open the 'Sisense Activation' application as an administrator: 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.
VseslavSivakPosted 9 months ago
0
Sisense Administration
Deploying an internet-facing ALB for a private Amazon EKS cluster
Step-by-Step Guide: To create an ALB with a private EKS cluster 1. Create a private EKS cluster. In our case, we used eksctl, so we added privateCluster: enabled: true Since our route is going through the NAT Gateway, we added it and specified that we will use only private subnets vpc: nat: gateway: Enable subnets: private: us-east-2a: id: subnet-0000000000000001 us-east-2b: id: subnet-0000000000000002 us-east-2c: id: subnet-0000000000000003 For node groups, we specified privateNetworking: true 2. Deploy ALB controller https://docs.sisense.com/main/SisenseLinux/using-an-aws-load-balancer-controller-with-sisense-on-amazon-eks.htm Attach IAM Roles to the EKS node groups by specifying the following arguments to the script: EKS_NAME: Your EKS Cluster name EKS_REGION: The region where the EKS is located NAMESPACE: (optional) Target namespace for ALB controller; by default, it will be installed in the “default” namespace curl https://data.sisense.com/linux/scripts/aws-alb-iam-attach.sh | bash -x -s <EKS_NAME> <EKS_REGION> <NAMESPACE> Edit extra installation values vim ./installer/extra_values/installer/installer-values.yaml Note- Since our worker groups are in private subnets, we must specify the public subnets in Kubernetes annotations. alb_controller: enabled: true hostNetwork: false certificate_arn: "your_certificate_arn" annotations: alb.ingress.kubernetes.io/target-type: ip alb.ingress.kubernetes.io/auth-session-timeout: 604800 alb.ingress.kubernetes.io/subnets: subnet-public-0,subnet-public-1,subnet-public-2 #alb.ingress.kubernetes.io/healthcheck-timeout-seconds: 5 #alb.ingress.kubernetes.io/healthcheck-interval-seconds: 15 Your public subnets should be tagged with kubernetes.io/role/elb = 1 Keep in mind that you have to set cloud_load_balancer: false is_ssl: false In cloud_config.yaml 3. Install Sisense ./sisense.sh cloud_config.yaml References/Related Content https://docs.sisense.com/main/SisenseLinux/using-an-aws-load-balancer-controller-with-sisense-on-amazon-eks.htm https://docs.sisense.com/main/SisenseLinux/using-an-aws-load-balancer-controller-with-sisense-on-amazon-eks.htm Conclusion: This is how you can configure an internet-facing Application Load Balancer (ALB) for a private Amazon EKS cluster. 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.
Liubomyr DykyiPosted 10 months ago
0
Sisense Administration
How to use SI CLI commands without a Linux host [Linux]
Step-by-Step Guide: 1. Get the management pod name by running the following command: kubectl -n sisense get pods -l app=management -o name 2. Connect to this pod using the name from the previous output (underlined), e.g. kubectl -n sisense exec -it pod/management-764c66fbc4-td4db -- bash 3. Import the sisense.sh script: source /etc/sisense.sh 4. Log in to your Sisense instance with the following command (please keep in mind that the URL will be resolved via DNS, so it must be resolved correctly from this particular environment): login_sisense https://YOUR_URL (or http://YOUR_URL:port) 5. Provide your Sys.Admin credentials on the prompt 6. As soon as you get the ‘Login succeeded’ message, you are able to run SI CLI commands Conclusion: Despite the fact that we are not aware of any issues while running SI commands from the management pod, we still recommend using a dedicated Linux host as a bastion for such purpose. References/Related Content https://docs.sisense.com/main/SisenseLinux/using-sisense-cli-commands.htm 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.
Oleg ValynkinPosted 10 months ago
0
Sisense Administration
Clean cached RAM

Clean cached RAM This article will discuss how to clean cached RAM on a Linux system. We’ll see how to carry out the clean-up process manually. We’ll make use of tools such as Grafana and echo. Linux is borrowing unused memory for disk caching. This makes it look like you need more memory, but you do not. In Sisense, you can check it in Grafana Dashboard Node Exporter / Nodes. Disk caching makes the system much faster and more responsive. It does not take memory away from applications in any way, ever. If your applications want more memory, they will take back a chunk that the disk cache borrowed. The disk cache can always be given back to applications immediately-- you are not low on ram. You cannot disable disk caching; the only reason anyone wants to disable disk caching is that they think it takes memory away from their applications, which it doesn't. Disk cache makes applications load faster and run smoother, but it never takes memory away. So, there's no reason for you to disable it. Kernels 2.6.16 and newer provide a mechanism to have the kernel drop the page cache and/or inode and dentry caches on command, which can help free up a lot of memory. To use /proc/sys/vm/drop_caches, just echo a number to it. To free pagecache: # echo 1 > /proc/sys/vm/drop_caches To free dentries and inodes: "# echo 2 > /proc/sys/vm/drop_caches To free pagecache, dentries and inodes: echo 3 > /proc/sys/vm/drop_caches This is a non-destructive operation, and will only free things that are completely unused. Dirty objects will continue to be in use until written out to disk and are not freeable. If you run "sync" first to flush them out to disk, these drop operations will tend to free more memory. After Memory Clean with the echo 3 > /proc/sys/vm/drop_caches , you`ll observe the free RAM increase in Grafana: This article discussed how we could clean up the cached RAM of our Linux system. Once you need to clear some RAM quickly to workaround another issue, like a VM misbehaving, you can force Linux to drop caches non-destructively.
OleksandrPosted 3 years ago • Last reply 11 months ago
2
Sisense Administration
GIT Instruction How To

GIT Instruction How To In order to migrate Sisense assets between environments, please follow the below steps: Step to add your assets to the GIT repository: 1. Create a project by adding a project name along with a default branch name (such as master, POC, or any meaningful name) 2. Add your GIT repository which could be remote or local. Below screenshot shows remote repository: 3. When you execute the test to GIT, the system will show connection was successful. 4. You can either choose the option to create and continue or create and close buttons 5. You can either share your project with others or continue to the next step: 6. At this point, you have two options to add Assets. You can add one in below screen and add it to your project: 7. Or you can save the project close, and add asset by clicking “managing asset” 8. After adding your assets, we should choose the project: 9. Then select all uncommitted changes; add a comment for your added assets and commit the new changes. 10. Now you push the assets so the newly added objects will be sent to the repository. 11. The Sisense application will need your GIT application credentials to proceed: Steps to add assets from GIT to another instance: 1. You will need to create a project in the second instance: Click create project and continue 2. At this step, you can share the new project with other team members if needed: Save and close the project. 3. Then choose pull from your GIT repository and make sure you add the correct branch as seen in below screenshot: 4. The system again will ask for credentials: Where the pull action, will ask for credentials: 5. And it will update the project: 6. You will then need to pull your added Assets and add your note; and commit afterward: You should then see your assets in the prod instance. In our ex ample, map elasticube was added. For more information, you can check out the following Articles: https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-git-integration.htm https://www.sisense.com/platform/git-integration/ https://community.sisense.com/t5/knowledge/elevate-your-data-product-s-quality-with-streamlined-version/ta-p/15131
Vicki786Posted 1 year ago • Last reply 11 months ago
3
Sisense Administration
Backing up and restoring Sisense
Backing up and restoring Sisense Introduction The article is meant to be a companion to the Sisense Backup and Restore documentation . The Sisense documentation provides the details on how to backup and restore Sisense. This article will provide additional information and give recommendations. Application versions This article applies to all Sisense Linux self-hosted versions. It does not apply to any Sisense Windows versions, nor to any managed service (Sisense hosted) versions. For Sisense-hosted versions, Sisense Cloud Operations takes care of creating all backups. Overview Regularly backing up the Sisense application Ensures that the Sisense application can be readily restored in the case of a hardware or other system failure. A backup should be taken before an upgrade. In case there are any issues with the upgrade, the upgrade can be rolled back. When installing Sisense on new machines, a backup can be taken to easily migrate Sisense between the old and new infrastructure. What is included in the backup The following assets are included in the Sisense backup Branding (opt/sisense/branding) - Files related to customized branding Build-plugins (opt/sisense/build-plugins) - Any custom post build plugins Connectors (opt/sisense/storage/connectors) - Connectors in use, including any custom JDBC connectors Custom-certificates (opt/sisense/storage/custom-certificates) - security certificates Data (/opt/sisense/storage/data) - Any specialized data files that may have been added Emails (/opt/sisense/storage/emails) - Email templates External-plugins (/opt/sisense/storage/external-plugins) Mongo_dump - This includes backups of all Sisense MongoDB databases used to support the Sisense application. Note that this does not include any customer-created MongoDB databases. Notebooks (/opt/sisense/storage/notebooks) Plugins (/opt/sisense/storage/plugins) include plugins included with Sisense as well as any custom plugins. Build Schedules - The schedules for all scheduled builds Server Side Plugins (/opt/sisense/storage/serverSidePlugins) Tenant-specific files - This includes static files related to elasticubes, such as CSV and XLSX. Note that even if the tenants feature is not being used, there is still a system tenant where elasticube static files are stored. Translations (/opt/sisense/storage/translations) - Files to support Sisense in multiple languages. Files for any additional languages would also be here. Usage (/opt/sisense/storage/usage) - Files related to usage analytics Configuration settings Running a backup There are two ways to run a backup. Using the CLI commands . Using the v2.0 Backups REST API. Note that backups done through the rest api are limited to 2GB in size. The Sisense backup can be configured to include the elasticube data with the ‘-include-farm’ flag. I recommend that the elasticube data not be included in the backup for routine backups. Depending on how often the backups are run, the elasticube data will probably be out of date by the time the backup is restored to a new environment. It is better to run builds for each elasticube to get the latest data. Extra paths can be included in order to backup folders that are not included by default (see above). This can be done via two methods. Add them through Sisense Configuration (in the admin tab). Once in configuration, scroll down to the management section and add the paths in the ExtraBackupPaths field. The advantage of this is that the extra paths will be included for every execution of the backup. The paths can also be added at run time with the -include-extra-paths yes flag and specifying the extra paths. The extra paths will only be included for the specific execution of the backup. By default, the Sisense backup is stored in /opt/sisense/storage/system_backups. This folder can be accessed from the Admin/File Management GUI. In a single-node environment, the system_backups folder can be accessed directly from the Linux host OS. In a multinode environment, you must exec into the management pod in order to access the /opt/sisense file structure. To do that, you can run the following kubectl command kubectl -n sisense exec $(kubectl get pod -l app.kubernetes.io/name=mongodb -o name -n sisense) -c mongodb -it -- bash Checking on the status of a backup You can check on the status of an existing backup (and see other backups) through the CLI backup-list command. The in-progress backup will show with a status of ‘Running’ in the output si system backup-list [ ALT Text: A terminal screen shows a backup list with columns: Backup name, creation time, size, and status. Most are succeeded, one is running.] Exporting the backup file Since one purpose of the backup is the ability to restore the Sisense instance in case of hardware or other failure, having the backup files on the Sisense file system will be problematic in case of a system failure. Fortunately, the Sisense backup process supports writing the backup to an s3 bucket with a flag -to-s3 true . To configure the S3 bucket within Sisense, follow these steps. If you don’t already have an S3 bucket, create one in AWS. Public access should be blocked, and a bucket policy should be set with the minimum access necessary for the S3 bucket. A Sid of ‘AllowWriteFromSpecificIP’ or similar rule can be used to ensure that only the Sisense server can write to the S3 bucket. Set the configuration through the CLI. Once you have logged into the CLI, run the following commands to set the configuration fields. si config set -key management.S3BackupBucket -new-value <BucketName> si config set -key management.AWSAccessKey -new-value <AccessKey> si config set -key management.AWSSecretKey -new-value <SecretKey> If you are not using S3 buckets, then it is best practice to copy the backup from the system_backup folder to a location outside Sisense. Scheduling the backup The backup can be scheduled using the CLI with the command si schedulers backup create -cron-expression <cron expression> -retention <number of backup copies to retain>. For information on cron expression format, please see crontab guru . Restoring from a backup A Sisense backup file can be easily restored onto an existing Sisense installation. If restoring the backup to a new instance, first perform a Sisense installation. A Sisense backup can be restored to the same version of Sisense or three versions higher. Running a restore A restore can be run through the Sisense CLI . The syntax is si system restore -name <backup-name> The backup name is the file name without the extension tar.gz. The name of the backup can be seen through the CLI backup list command si system back-list [ ALT Text: Terminal screenshot listing system backups with columns for Backup Name, Creation Time, Size, and Status. All entries show "SUCCEEDED" in green.] The restore command assumes that the backup file is in /opt/sisense/storage/system_backups. This is the default location where the backup file is stored. If the backup was originally stored to s3 using the s3 flag then it can be restored from s3 using the flag -from-s3 true The extra paths syntax that was used for the backup should be used for the restore. Testing the restore If the backup is part of a disaster recovery strategy, restoring the backup should be done on a regular basis as part of a disaster recovery drill. You don’t want to wait for a real disaster to find out that there’s a problem with the backup file. Conclusion The backup and restore process is an important part of your Sisense business continuity plan. As an application-level backup, the Sisense backup is independent of the underlying OS version. This makes it useful for backing up and restoring Sisense between different servers and environments. References Backing Up and Restoring Sisense Using the Sisense CLI Cron Format
David EhrlichPosted 1 year ago
0
Sisense Administration
Update and add new Highcharts modules for use in Sisense plugins

Update and add new Highcharts modules for use in Sisense plugins The JavaScript library framework Highcharts is natively included in Sisense and is utilized in many native Sisense widgets as well as in numerous Sisense plugins. Although Sisense typically does not alter the Sisense Highcharts library version with every release, the versions of Highcharts included in Sisense may change when upgrading to a new major version release. Highcharts can load additional chart types and other types of functionality via JS module files that contain code-adding features such as additional chart types, which can be used within plugins along with additional code to create additional widget types. If a plugin utilizes a Highcharts module, you can source the module directly in the "plugin.json" file's source parameter, as shown in this example: "source": [ "HighchartModule.js", ], To determine the current Highcharts version being used in your Sisense version, you can use the "Highcharts" command in the web console while viewing any page on your Sisense server. After identifying the current Highcharts version, you can find the corresponding module hosted on the Highcharts code hosting website using the following URL format: https://code.highcharts.com/${Highcharts_Version}/modules/${module_name}.js For example: https://code.highcharts.com/6.0.4/modules/heatmap.js You can save this module and upload it to the plugin folder or replace the older module JS file simply by copying and pasting the code directly. Be sure to update the "plugin.json" file to point to the new module file if the file name has changed or if this is the first time the module is included. Simply sourcing the module file in the "plugin.json" file is sufficient to load the module into Highcharts; no further code is required to load the module.
Jeremy FriedelPosted 2 years ago • Last reply 1 year ago
2
Sisense Administration
How to make a dashboard as the first page of the analytics tab

How to make a dashboard as the first page of the analytics tab Introduction: How to add the dashboard/site as the first page of the Analytics tab with the help of the Branding. Step-by-step guide: Create a dashboard based on the BLOX, for example Share this dashboard with the group Everyone Press 3 dots on the top right of the dashboard, select Embed code, and select the following checkboxes on the float window [ALT Text: The image shows the "Embed Dashboard" settings for a Sisense dashboard. It includes options to customize the embed settings, such as toggling the right panel, left panel, toolbar, and header. The URL code at the bottom updates based on the selected options. The unchecked options suggest that the embed link is being customized to hide specific UI elements in the embedded dashboard.] Copy the URL Code Paste it to the Admin - App configuration - White labeling - Analytics & Data Main pages - Analytics Home Page or Admin - Server & Hardware - Management - Configuration - Branding - Home Page (Be sure that toggle Enable Branding is enabled) Press the Save button to save the changes Check with a user who has Viewer permission To add the site, you should just paste the URL of the site into the Home Page field. Just remember that, based on the security, that site should allow use if with Iframe from other domains - X-Frame-Options: ALLOW-FROM origin ( https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options ) To check this, you can use the https://example.com site Refrences Sisense Docs
OleksandrBPosted 1 year ago
0
Sisense Administration
Understanding Java licensing for Sisense insight installation

Understanding Java licensing for Sisense insight installation Introduction This article addresses the Java licensing requirements for using Sisense Insight installations. Users frequently inquire whether the Java Runtime Environment (JRE) included with Sisense is covered by Sisense or if they need to transition to an alternative such as Azul Java , especially in light of Oracle Java's licensing constraints. Step-by-Step Guide Understand the Licensing Context: Oracle Java versions beyond version 6 have specific licensing requirements that may impose restrictions if not covered under a third-party agreement. Check the Installed Java Version: For Sisense 2023.3 , Java version 8 is typically included. Always review the version details included with your specific Sisense installation. Verify Licensing Coverage : О Sisense generally provides a compatible Java Runtime Environment with its installations. However, it's essential for users to confirm if this coverage satisfies their organizational requirements , especially if bound by any Oracle Java restrictions. Consider Alternative Java Providers: If the installed Java version does not meet licensing requirements, consider transitioning to a supported alternative like Azul Java. Refer to Release Notes: O Always check the latest release notes for specific Java version details included in each Sisense version. Visit: Sisense Release Notes Conclusion To ensure compliance with Java licensing, confirm whether the Java version provided with your Sisense installation meets your licensing needs. Keep abreast of version-specific details through the provided release notes and seek alternatives if your version does not meet your requirements. References/ Related Content Oracle Java Licensing Details Azul Systems - Java Solutions Sisense Support and Documentation 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.
Vicki786Posted 1 year ago
0