There is a known issue that is planned to be fixed in the Sisense L2023.6+. If you install Sisense on CentOS or RHEL version >= 8 the old EPEL 7 repositories are used instead of EPEL 8 To fix this issue: Locate in the installation folder and open i...
Kubernetes DNS Linux issue caused by missing br_netfilter kernel moduleWhat You’ll LearnIn this course you will learn how to:How to troubleshoot DNS issues in KubernetesHow to check if the br_netfilter kernel module is installed on the nodeHow to mak...
Websocket Functionality Within SisenseIntroductionSisense uses the WebSocket Protocol to load dynamic content within the platform. It’s important to remember that the WebSocket Protocol is simply an upgrade of HTTP(S) traffic, relying on the same bas...
Sisense Linux Multinode: MongoDB, Zookeeper and Data Recovery Problem: In unfortunate circumstances, there are situations where a Sisense Linux Multinode instance can become corrupted and the only choice to move forward is reinstallation. Sometimes i...
Report Manager: Most Common Troubleshooting Steps Sisense has gone through and collected the most commonly reported issues related to the Report Manager plugin. Save time and effort by reading through the most common Report Manager plugin troublesho...
Triaging Build Failures Symptoms Sometimes during a build, you can encounter an error or two. Below are two common build failures you might experience and steps you can take to resolve the problem quickly. "BE#967529 Failed to connect to new ec: <cu...
Symptoms Relevant for Linux Below are a couple of select symptoms your system could be experiencing under a big load with simultaneous builds. Please note the list is not exhaustive: Build failures over random cubes or a couple of cubes that are bei...
Symptoms Relevant for Linux Single-node Sisense In a default Sisense single-node deployment, there is one pod per service deployment. In cases of heavy usage, which is usually caused by parallel requests, the number of services processing the reque...
