How to properly reboot a k8s node(s)
As part of maintaining a healthy and robust Kubernetes (K8s) cluster, occasional reboots of nodes might be necessary. Whether for system updates, hardware maintenance, or other reasons, it's essential to follow a structured process to ensure minimal disruption to running workloads. Below is a step-by-step guide on safely rebooting nodes within a Kubernetes cluster, covering both Red Hat Enterprise Linux (RHEL) and Ubuntu systems.7.6KViews2likes0Comments
Is it possible to change the scroll bar color?
I have several pivots and tables that require scrolling through. Given that I have a dark background, the scroll bar is hard for users to see. I’d like to change the color to improve the user experience. Ideally, this would be done at a high level, but I would also be happy with any JS to do it at the widget level.4.7KViews0likes6Comments
Schedule "Changes only" EC build
Hello, Is there a way to schedule a "Changes only" build in Sisense? As per the article below, it appears that there is no option to select what type of build I want to run. By default it runs a "Replace All" build at the scheduled time. I wish to run a "Changes only" build at the scheduled time. Any insights? Thanks! https://documentation.sisense.com/w2022-3-x/docs/scheduling-buildsSolved3.5KViews0likes3Comments
Client Specific Custom Fields - Dynamic Field Names (Metadata Translator)
Hello, our clients create their own custom fields and I would like to display them in Sisense with their client-specific names. I have followed the directions in this article implementing the Metadata Translator but the documentation about the plugin has been removed and I am having difficulty getting it to work. https://support.sisense.com/kb/en/article/how-to-work-with-client-specific-custom-fields Is anyone successfully using the Metadata Translator plugin? Any tips on how you got it to work? Or know of any other solutions for dynamic field names? Thanks in advance!3.2KViews0likes2CommentsCustomize Pulse notification alerts
Hello! I have Pulse notifications setup for build alerts. The default alert notification only indicates whether a build was success or failure. In an event a scheduled build has failed, is there a way to customize the build alert notifications to include the error message from the log file indicating why a scheduled build has failed ? On the Pulse page, I see an option to "Edit Script". Clicking on the option opens up the Script editor with the following message (see below). However, I did not find any additional details on the developer page. Any help is much appreciated. Thank you! /* Welcome to your Alert's Script. To learn how you can access the Alert object, see the online documentation at http://developer.sisense.com/display/API2/Pulse+API */Solved3KViews0likes2CommentsBuilding Cube - Long Time Initializing and Finalizing
My cubes can take 15-20 minutes during the initializing and finalizing steps when building. This is out of the 25-30 minutes it takes to do the entire build - so over 50% of our build time is coming from these steps. Does anyone have an idea what could cause this and ways to shorten the time it takes to complete these steps? Additional info - we are cloud hosted, our cube builds are staggered so there is never more than one cube building at a time, and all builds are Replace All. Thanks in advance!2.8KViews0likes2Comments
How to properly reboot a k8s node(s)
As part of maintaining a healthy and robust Kubernetes (K8s) cluster, occasional reboots of nodes might be necessary. Whether for system updates, hardware maintenance, or other reasons, it's essential to follow a structured process to ensure minimal disruption to running workloads. Below is a step-by-step guide on safely rebooting nodes within a Kubernetes cluster, covering both Red Hat Enterprise Linux (RHEL) and Ubuntu systems.
