Tabber - Troubleshooting The Most Common Issues
Tabber - Troubleshooting The Most Common Issues Introduction This article provides troubleshooting steps for the most common issues with the Tabber add-on. Search for the relevant symptom and review the solution that might help resolve the issue. Step-by-Step Guide Symptom: The Tabber widget is not displayed in the list of widget types. Solution: This issue could be related to plugin build problems. Please follow the steps outlined in this troubleshooting guide: Resolving Plugin Build Issues. Symptom: A dashboard with many widgets under Tabber loads slowly. Solution: Loading a dashboard with Tabber loads all widgets, even if they are not displayed under a specific tab. Move some widgets to a separate dashboard and consider using the JumpToDashboard add-on. Refer to the guide on how to use the JTD plugin: JumpToDashboard Plugin - How to Use and Customize. If this does not resolve the issue, please refer to the Troubleshooting Performance Issues guide. Symptom: A custom script used to customize widget functionality with the add-on stopped working after an upgrade, or a widget with Tabber is malfunctioning. Possible symptoms of such an issue include incorrect UI behavior when navigating between tabs, wrong highlighting of the tabs, or widget resizing issues. Solution: Remove the custom script from the widget to verify if the native Tabber functionality works correctly. If it does, the issue is caused by the custom script, which should be reviewed by its developer. Symptom: Tabber script configurations stopped working after an upgrade. The UI of the Tabber add-on is different from the previous version. Solution: Starting from Tabber version 1.2.0 (included in Sisense version L2024.2 and later), configuration parameters supported in the UI are ignored in the script. However, the widget script functionality remains available (as with other widgets), and script code unrelated to Tabber configurations will still execute. If you encounter issues with widget display after updating to Tabber version 1.2.0 or newer, you can revert to configuring the widget via script by adding the following parameter: widget.scriptConfig = true; To return to using UI configuration, change the property to false. Please refer to the Tabber guide for more details. Conclusion The Tabber add-on is a versatile tool for managing and organizing widgets in Sisense. While it is designed for reliability, certain scenarios may require troubleshooting to maintain optimal functionality. This guide provides clear solutions to common issues, helping you address them effectively. For additional support, consult Sisense community resources or reach out to the Sisense support team.How to Troubleshoot UI Issues Using DevTools (HAR File & Console Logs)
If a webpage, dashboard, or widget isn't loading properly, encounters errors during exporting, importing, editing, or opening, or if buttons are unresponsive and error messages appear, you can use Developer Tools (DevTools) in your browser to diagnose the issue. This guide will show you how to: - Check the Network tab for failed requests. - Use the Preview and Response tabs to see details of errors. - Check the Console tab for other issues. - Save a HAR file to share with support.Resolving plugin build issues
Resolving plugin build issues Introduction This guide provides step-by-step instructions to address common issues with plugins failing to compile. Possible symptoms of this issue include a newly added system add-on not appearing or changes made to the add-on files not being reflected in the UI. By following these steps, you can troubleshoot and resolve the problem. Steps to Resolve Issues For Cloud-Managed Services (Linux) Locate the last uploaded add-on in the plugins directory and try to remove it (ensure you make a backup copy of this folder beforehand). To do this: - Open the Admin tab. - Navigate to System Management > File Management (under Server & Hardware) > plugins directory. - Sort plugins by their last update date to identify which ones might potentially cause issues. 2. Go to the Add-ons page under the Admin tab and try to disable/enable any add-on to check if the plugin's build process starts. If the process is running, you will see a message like “Add-ons build in progress” at the top right corner of the page. 3. If the issue persists, contact the Support team for further assistance. For On-Premises Deployments (Linux) Locate the last uploaded add-on in the plugins directory and try to remove it (ensure you make a backup copy of this folder beforehand). To do this: - Open the Admin tab. - Navigate to System Management > File Management (under Server & Hardware) > plugins directory. - Sort plugins by their last update date to identify which ones might potentially cause issues. 2. Go to the Add-ons page under the Admin tab and try to disable/enable any add-on to check if the plugins build process starts. If the process is running, you will see a message like “Add-ons build in progress” at the top right corner of the page. 3. Restart the plugins service on the server using the following command: kubectl -n sisense delete pod $(kubectl -n sisense get pods -l app="build" -o custom-columns=":.metadata.name") 4. Check the status and events of the plugins pod on the server by using the commands provided in this guide “Sisense Linux CLI Commands”: https://docs.sisense.com/main/SisenseLinux/linux-supported-cli-commands-for-sisense.htm?TocPath=Troubleshooting%20%26%20Best%20Practices%7C_____6 5. Review the RAM consumption of the plugins pod in Grafana: - Open the Admin tab. - Navigate to System Management > Monitoring > Dashboards, and choose All pods per namespace. - On the dashboard, select Namespace = Sisense and the relevant pod (e.g., plugins-{unique identifier}). - Check the Memory usage graph (default RAM limit is 1536 MB). 6. If you encounter OOMKilled errors or high RAM consumption for the plugins pod, refer to the troubleshooting steps outlined here “Add-ons Service Memory Consumption”: https://docs.sisense.com/main/SisenseLinux/sisense-add-ons.htm#AddonsServiceMemoryConsumption:~:text=a%20paid%20service.-,Add%2Dons%20(Plugins)%20Service%20Memory%20Consumption,-The%20add%2Dons For On-Premises Deployments (Windows) Locate the last uploaded add-on in the plugins directory: C:\Program Files\Sisense\app\plugins (for V7.2+), and try to remove it (ensure you make a backup copy of this folder beforehand). Restart the Sisense.Plugins service. To do so: Open Task Manager Navigate to the Services tab. Restart the Sisense.Plugins service. Follow this guide for more details “Restart All Sisense Services”: https://docs.sisense.com/win/SisenseWin/restart-all-sisense-services.htm Conclusion Following this guide helps resolve plugin compilation issues by targeting common problems such as insufficient memory allocation, stuck build processes, or service malfunctions. For further assistance, always consult the official documentation or contact your support team. Related Content Sisense Linux CLI Commands: https://docs.sisense.com/main/SisenseLinux/linux-supported-cli-commands-for-sisense.htm?TocPath=Troubleshooting%20%26%20Best%20Practices%7C_____6 Add-ons Service Memory Consumption: https://docs.sisense.com/main/SisenseLinux/sisense-add-ons.htm#AddonsServiceMemoryConsumption:~:text=a%20paid%20service.-,Add%2Dons%20(Plugins)%20Service%20Memory%20Consumption,-The%20add%2Dons Restart Windows Services: https://docs.sisense.com/win/SisenseWin/restart-all-sisense-services.htm
