How to identify and download logs from the Sisense server
To identify and download ec-bld logs in Sisense, first, log into the Sisense server and run kubectl -n sisense get pods | grep bld during the cube build to find the relevant pod name. Once the build is complete, locate the log file in /var/log/sisense/sisense/ (for single-node) or use kubectl cp commands to retrieve logs from fluentd or management pods (for multi-node). Finally, access the Admin File Manager > Data folder to download logs and clean up local copies if needed.How to record a .har file and identify if specific requests are present in logs
To record a .har file in Chrome, open Developer Tools > Network tab, enable recording, clear logs, and reproduce the issue before exporting the file. To check for jaql requests, filter by "jaql" in the Network tab and inspect the request status and X-Request-ID. For on-premise Sisense, use cat /var/log/sisense/sisense/<log_file_name> | grep <X-Request-ID> (single-node) or kubectl exec (multi-node) to search logs for the request.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.How to check specific pods CPU/memory consumption in Grafana
To check pod CPU and memory usage in Grafana, go to Dashboards > All Pods per Namespace, select sisense, adjust the time frame, and filter by pod name. Ensure CPU and memory graphs are visible in screenshots, taking separate ones for different pod types.How to resolve browser freezing issues (page unresponsive) on your dashboards
This article addresses the issue of web pages freezing and becoming unresponsive when users interact with certain Sisense dashboards. It typically occurs when applying filters or interacting with heavy widgets, which can significantly impact the usability of critical dashboards. The error says "Page Unresponsive":Resolving Build Failures Due to Memory Issues [Safe-Mode]
This is the guide of which settings should be checked and adjusted to resolve the problem and prevent future occurrences, in cases when cubes fail with the error ‘Safe-mode’. Please follow the steps below, and after that try to re-build the failed cubes.Connection Tool - Programmatically Remove Unused Datasource Connections, and List All Connections
Managing connections within your Sisense environment can become complex over time, if there are a large number of connections, and connections are often added, and replace earlier datasource connections. In some scenarios unused connections can accumulate, potentially cluttering the connection manager UI with no longer relevant connections. Although unused connections typically represent minimal direct security risk, it's considered best practice to maintain a clean, organized list of connections, and in some scenarios it can be desired to remove all unused connections. Sisense prevents the deletion of connections actively used in datasources, safeguarding your dashboards and datasources from disruptions. However, inactive or "orphaned" connections remain after datasources are deleted or a connection is replaced, potentially contributing to unnecessary UI complexity in the connection manager UI. Connections can be of any type Sisense supports, common types include various SQL connections, Excel files, and CSV files, as well as many data providers, such as Big Panda. This tool can also be used to list all connections, with no automatic deletion of unused connections.
