Sisense Community

Community Feedback
Chapters
Events
Forums
Blogs
KB Docs
Support
Learning
Use Case Gallery

Categories

Emails Reporting

Sisense Partners

Ido Darnell
Pixel-perfect design and reporting for Sisense, a review of available options

If you manage Sisense, you've had some version of this conversation: someone asks for a report that actually looks like a finished document, not a dashboard screenshot with the edges cut off. There are more ways to solve this than most admins realize, and each one solves a different piece of the problem. A quick rundown: Native PDF export - zero setup, but the layout is whatever the dashboard happens to produce. No control over page breaks, no way to add narrative text, and pivot tables cut off at the edge of the screen. Sisense Report Manager - solid scheduling and delivery, but it's still exporting the dashboard as-is. No design layer, no multi-dashboard composition. Jasper Reports - genuinely pixel-perfect for table and pivot widgets specifically, if you have developer resource to build and maintain JRXML templates. Doesn't touch charts or KPI widgets. SAP Crystal Reports via ODBC - full design control, but it pulls your data out of Sisense entirely to do it, which is a real consideration if data residency matters to you. Where this leaves most teams: something that handles scheduling, or something that handles pixel-perfect tabular data, but not both, and rarely anything that lets you design a report as its own document rather than a dashboard export. That's the gap QBeeQ Report Studio is built for: a canvas inside Sisense where you design the report as a report - pulling from multiple dashboards if you need to, with full control over layout, brand, and every widget on the page. Report Studio Deliver , our scheduled distribution layer, is coming in beta this month. For the full breakdown with a side-by-side comparison table, here's the complete write-up .
1 week ago
0
Troubleshooting
[Custom SMTP Email Server] - Google SMTP - 534-5.7.9 Application-specific password required

[Custom SMTP Email Server] - Google SMTP - 534-5.7.9 Application-specific password required When using GoogleSMTP with Sisense, you might encounter an issue where emails stop being received, and the logs display the following error message: 534-5.7.9 Application-specific password required. This occurs because, if you have enabled 2-factor authentication on your Google account, you cannot use your regular password for programmatic access to Gmail. Instead, you need to generate an app-specific password to use in place of your actual password. An app password is a 16-digit code that allows a less secure app or device to access your Google Account. These passwords are only applicable to accounts with 2-Step Verification enabled. Steps: Log in to your Google account. Navigate to My Account > Sign-in & Security > App Passwords (you may need to sign in again to confirm your identity). Scroll down to the "Select App" section (within the Password & sign-in method box) and choose "Other (custom name)". Name the app password, for example, "nodemailer". Click "Generate". Copy the generated password and paste it into your Node.js script in place of your actual Gmail password. Related content: For more detailed information about Gmail SMTP errors and codes please check out this article: https://support.google.com/a/answer/3726730?hl=en Setting Up Custom Email Servers
Vladyslav HontarPosted 1 year ago
0
Troubleshooting
Scheduled Email Randomly not sent

Scheduled Email Randomly not sent when scheduled dashboard reports are sent via email. If you see several emails goes out correctly. And several mails did not sent or not recieved at all. You may want to try the following: 1) Increase the memory limits on the exporting pod by running: kubectl -n sisense edit deployment exporting -> under spec: -> containers: -> resources: -> limits: -> change memory from memory: 1000Mi to memory: 2000Mi 2) Check the Max memory limits defined for the reporting pod by running the following command: kubectl -n sisesne describe pod <pod_name> In case the memory limit is below 2000Mi, please increase it to 2000Mi using the following procedure: kubectl -n sisense edit deployment reporting -> under spec: -> containers: -> resources: -> limits: -> change memory from memory: 1000Mi to memory: 2000Mi 3) Please note that a pod restart is not required, it should be done automatically. After the pod was restarted please confirm that the containers of reporting and exporting pods were updated to memory: 2000Mi by running the command: kubectl -n sisense describe pod <pod_name> 4) Try to reproduce the issue to see if the memory increase affected the results If you still encounter any issues: 5) Check if there is a firewall configured between the SMTP server to Sisense server 6) Is there a local firewall configured (windows firewall or iptables) on the SMTP server 7) What is the timeout configuration on Sisense for the SMTP server - can be found at Admin tab -> Email server -> Connection timeout, Greeting timeout, and Socket timeout It is recommended to Please change the followng configurations of in the Admin Tab --> Email server --> SocketTimeout configuration: a) socketTimeout to 600,000 milliseconds b) the ConnectionTimeout to 120,000 milliseconds c) GreetingTimeout to 30,000 milliseconds. Try to reproduce the issue again to see if these setting increases affected the results or not. If you still encounter issues, please create a support portal and Attach the following logs to the ticket: Jobs.log - in /var/log/sisense/sisense/jobs.log Reporting.log - in /var/log/sisense/sisense/reporting.log Exporting.log - in /var/log/sisense/sisense/exporting.log Galaxy.log- in /var/log/sisense/sisense/galaxy.log Api-gateway.log - in /var/log/sisense/sisense/api-gateway.log Identity.log - in /var/log/sisense/sisense/identity.log
Vicki786Posted 1 year ago • Last reply 1 year ago
1
Troubleshooting
Email Troubleshooting

Email Troubleshooting NOTE: This is an updated version of the following community article - https://community.sisense.com/t5/knowledge/email-troubleshooting-sisense-7-2/ta-p/8941 This guide will demonstrate a few official first steps for troubleshooting many of the common issues that we see with the email portion of the Sisense Application. This guide was written for version L2023.9, however, most of it can be applied to newer and later versions as well as to Windows versions . Please follow all of the relevant steps in this article to troubleshoot the issue initially, and, if after performing these steps you still experience an issue, our support team will be more than happy to assist you. Official Documentation First of all, we have great articles for basic Email troubleshooting for both Windows and Linux versions. Please make sure to check it first: Linux https://docs.sisense.com/main/SisenseLinux/troubleshooting-emails.htm Windows https://docs.sisense.com/win/SisenseWin/troubleshooting-emails.htm In case the suggestions from the above articles did not help or are not related to your issues, please proceed to step 2. Test basic email Run a test email. You can do it in Admin -> Server & Hardware -> Email Settings -> Send a Test email. Only available in Linux; for Windows, you can run a test report as described in the article from step 1. This will help us understand whether an email from Sisense can reach you. If you get an email, proceed with the next step. If you don't, proceed to step 6 and 7. Test Basic Report Create a very simple dashboard with 1 light widget. Try to send it as a report. This might help us understand whether the issue is not with a specific report or the report being too heavy. Disable Custom Email Server If you are using Custom Email Server, try to disable it. You can do it by going to Admin -> Server & Hardware -> Email Settings -> disable Enable Custom Email Server toggle -> save. After a minute test email sending as described in step 2. This might help us understand whether the issue might be with the specific Email Server. Check Plugins and Scripts Once we have confirmed that the emails are turned on, and we expect to see emails, the next step is to disable all of the plugins on the server for another round of testing. Common reasons for email failures: Unsupported, community plugins Out of date version of the officially supported plugins Custom scripts Go to Admin -> Server & Hardware -> Add-ons. Disable all plugins and wait a couple of minutes for the pods to restart. After that send test reports again. If the email comes through successfully, then walk through the plugins testing all possible plugin combinations until you are able to determine exactly which plugin is the culprit of the issue. If the plugin is an officially supported plugin, check to see if there is a newer version to install, and if there isn't a newer version, please open a support ticket documenting the exact replication steps and plugin name for our product team to update. If the plugin is an unsupported community plugin, look through the comments on the page to see if the author has updated the plugin recently or provided new code, and if not, feel free to comment on the page and see if the author is able to update the plugin or not. Repeat this same process for any custom dashboard or widget scripts as well. Restart Services Sometimes, for a variety of reasons, a service reset may be required by the system. Please perform the restart of the following services and after a couple of minutes test emails functionality once again. For Linux: Galaxy, Reporting, Jobs You can do it with the following command: kubectl -n sisense delete pod {name of the pod} To get the full name of the pod: kubectl -n sisense get pods For Windows: Galaxy, Jobs Go to Control Panel -> Administrative Tools -> Services -> Restart Sisense.Galaxy and Sisense.Jobs. Generally, it is a good practice to restart services regularly (once every couple of weeks); especially for reporting functionality. Contact Sisense Support If none of the steps above helped, please submit a ticket to Sisense Support. With the ticket, please provide the data about what is the exact issue and the steps taken to troubleshoot it. Additionally, attach the following information to the ticket: 1. Your Sisense version. 2. When did the issue start occurring? Were there any changes before that? 3. Zip the following log files together with a timeframe when the latest email failure occurred: (linux) /var/log/sisense/<Namespace>/reporting.log /var/log/sisense/<Namespace>/galaxy.log /var/log/sisense/<Namespace>/jobs.log (windows) (whole folder) C:\ProgramData\Sisense\application-logs
Vova ShenhoferPosted 2 years ago
0