How to identify and download logs from the Sisense server
How to identify and download logs from the Sisense server
Usually, you are provided with the list of logs needed for the investigation of your issue by the Sisense support team. They may include names of the file and, if you are experiencing build failures, ec-bld log of affected c
How to identify ec-bld log name for a particular cube
- Login to Sisense server
- While the cube is building, run the command: āŗ
1 kubectl -n sisense get pods | grep bld
You will see all bld pods for all active builds. You can identify the necessary bld pod since it will contain the cubes name in its name
For example:
Cubes name - Sample Healthcare
Possible bld pod name - ec-sample-healthcare-bld-c766573f-cd22-2
ā
For example ec-sample-healthcare-bld-c766573f-cd22-2.log
4. Wait for the build to finish before proceeding with downloading the l
How to download logs
You will follow different processes depending on whether you have a single-node or multi-node environment If you have a single-node:
- Login to the Sisense server
- Go to the folder with logs:
1 cd /var/log/sisense/sisense
ā
We will use query.log and ec-bld log of the particular cube as an example (we will use ec-sample-healthcare-bld c766573f-cd22-2.log, which we have identified in a section above). You need to substitute their names to the logs y need in this and all future steps.
1 ls -l | grep query.log
2 ls -l | grep ec-sample-healthcare-bld-c766573f-cd22-2
ā
1 cp query.log /opt/sisense/storage/data/query.log
2 cp ec-sample-healthcare-bld-c766573f-cd22-2.log /opt/sisense/storage/data/ec-sample-healthcare-bld-c766573f cd22-2.log
After these commands, there should be no output in the console
ā
[ALT Text: A screenshot of a command line interface displaying a series of text lines, predominantly in green on a black background, indicating some kind of terminal activity or output. The visible text appears to include file names and potentially command outputs but is mostly obscured or unclear due to formatting.]
5. In Admin tab open File Manager. There in āDataā folder you will find log files and will be able to download it from
[ALT text: A screenshot of a file management interface from Sisense. The top section displays a search bar and a list of files, including "example-file-name" and "canny.log," with details on their size and last modified date. The bottom section shows a similar layout, featuring a highlighted file named "example-file-name" with its size and a recent modification time. The color scheme includes a light background with blue and yellow accents.]
If you have a multi-node:
- Login to the Sisense server
- Find out the current directory (usually it's /home/ec2-user/) and copy it
1 pwd
[ALT Text: A blurred close-up of a computer terminal screen displaying a command line input in green text on a dark background. The command includes parameters such as "ec2-user" and file paths, suggesting interaction with an EC2 instance.]ā
3. Run the command
1 kubectl -n sisense get pods | grep -E 'fluentd|management'
You will receive the names of your fluentd and management pods. Copy the
ā
We will use query.log as an example. You need to substitute their names for the logs you need in this and all future steps.
4.1
1 kubectl -n sisense cp <your_fluentd_pod_name>:/var/log/sisense/sisense/<log_file_name> <current directory_name>/<log_file_name>
2 If namespace is other than 'sisense' the command will be:
3 kubectl -n sisense cp <your_fluentd_pod_name>:/var/log/<your_namespace>/sisense/<log_file_name> <current directory_name>/<log_file_name>
4 For example:
5 kubectl -n sisense cp fluentd-5b565b7b7c-462dr:/var/log/sisense/sisense/query.log /home/ec2-user/query.log
[ALT Text: A blurred image of a computer screen displaying code or text, with green characters on a dark background. The content appears to be technical in nature, possibly related to programming or data processing.]
4.2
1 kubectl -n sisense cp <log_file_name> <your_management_pod_name>:/opt/sisense/storage/data/<log_file_name> 2 For example:
3 kubectl -n sisense cp query.log management-765cbcf7bb-qr9mx:/opt/sisense/storage/data/query_00782680.log
[ALT Text: The image displays an abstract representation of text or code with a glowing green effect on a dark background, creating a digital or matrix-like appearance. The text appears to be distorted or scrambled, adding to the overall aesthetic.]
5.In Admin tab open File Manager. There is āDataā folder you will find log files and will be able to download them from
[ALT text: A screenshot of the Sisense dashboard displaying the File Management section. There are options on the left sidebar including "User Management," "App Configuration," and "File Management." The main area lists two files: "e-sample-whiteboard-0d16-7057-4E29-6B.jpg" and "query.bq," with their respective sizes and last modified time. A search bar is also visible at the top.]
6. Go back to the server and remove copied files from the local folder (usually it's /home/ec2-user/
1 rm <log_file_name>
2 For example:
3 rm query.log