Pulse troubleshooting guide (Linux)
Introduction:
This guide will help you troubleshoot common issues with Sisense Pulse Alerts on Linux.
Step-by-Step Guide:
Issue: Not Receiving Pulse Alerts
1. Check Pulse is Enabled:
- Confirm Sisense Pulse is enabled by checking the top menu for the "Pulse" tab.
If missing, a system administrator needs to enable it in the Admin page under Feature Management -> Pulse.
[Alt text: "Screenshot of Sisense admin panel showing Feature Management under App Configuration. Toggle switches for Pulse features are highlighted."]
2. Verify Notifications are Turned On:
- In Sisense, go to "Pulse."
- Check the alert tile. Ensure "Receive Notifications" is toggled on. If it's off, only other users will be notified.
[ALT Text: Dashboard displaying four data cards: a line graph with a menu highlighting "Remove Notifications," two showing costs of $789K, and a number "8,921".]
- For alerts disabled for everyone, look for shaded tiles and select "Turn On" from the Tile menu.
3. Confirm Alert Channels:
- In the alert settings, check the configured notification channels (Email, Mobile, Slack, Zapier, Webhook).
- Ensure these channels are correctly set up and accessible.
- Verify that email addresses, mobile numbers, or other channel configurations are accurate.
Check Alert Frequency Settings: - Sys Admins may have set a maximum alert frequency for live widgets. Confirm that this setting does not prevent alerts.
- If "Notify only once after a condition is met" is checked, you'll only get one alert per condition.
- If "Notify when a condition is no longer met" is checked, alerts are sent when the condition is no longer true.
4. Verify Thresholds and Conditions:
- Check the alert's threshold settings. Ensure the threshold is set correctly and the conditions are being met.
- For "Automatic" alerts, ensure the system has sufficient data to learn anomalies. The more data and builds, the more accurate the anomaly detection.
- For build alerts, check the "Notify when" condition (Build failed, Build succeeded, Build succeeded after failure).
5. Review Filters:
- In advanced alert settings, check the filters used for the alert. Ensure these filters do not exclude data that should trigger the alert.
Issue: Incorrect or Unwanted Alerts
- Review Alert Logic:
- Examine the alert's conditions and thresholds to ensure they accurately reflect what you want to be alerted for.
- Adjust Thresholds:
- Modify the threshold values in the alert settings if alerts are triggered too frequently or not frequently enough.
- Edit or Duplicate Alerts:
- If an alert is almost correct, duplicate it and modify the settings.
- Edit existing alerts to correct filters, names, or thresholds.
- Disable Unwanted Alerts:
- Turn off notifications for specific alerts you no longer need by toggling "Receive Notifications" in the "Pulse" page.
- Turn off alerts for all users by selecting "Turn Off" from the Tile menu.
[ALT TEXT: Dashboard with data widgets; one has settings open, highlighting "Turn Off" in red. Widgets display financial metrics, such as cost and averages.]
- Delete Unneeded Alerts:
- If an alert is completely unnecessary, delete it from the "Pulse" page by selecting "Delete" from the Tile menu.
Issue: Build Alerts Not Working
- Check Build Alert Setup:
- Ensure the build alert was created for the correct ElastiCube in the "Data" tab's List view.
- Verify Build Status:
- Check the ElastiCube build status. Build alerts are triggered based on "Build failed," "Build succeeded," or "Build succeeded after failure."
- "Notify once" Setting:
- If "Notify once when there is a status change" is selected, only one alert is sent per build status change.
Other Checks:
- Pulse Feed: Check the Pulse Feed in Sisense for recently triggered alerts.
[ALT TEXT: Notification panel showing two alerts. One indicates 199 unique Patient_IDs, time-stamped 23:51. The other confirms a successful eCommerce build, time-stamped 23:50. Users can clear all notifications.]
- Alert History: Review the alert history for past triggers and any potential errors.
[ALT TEXT: Chart displaying the number of unique Patient_IDs as 199. A horizontal line with a single data point is shown in the "History" tab.] - Permissions: Confirm you have the necessary permissions to view and manage Pulse Alerts.
Conclusion:
If you encounter issues not covered in this guide or discrepancies due to later releases, please contact Sisense Support for further assistance. This guide aims to help users effectively manage and utilize Pulse Alerts to stay informed about important KPIs and ElastiCube builds.
References/Related Content
https://docs.sisense.com/main/SisenseLinux/introduction-sisense-pulse-and-alerting.htm
https://docs.sisense.com/main/SisenseLinux/sisense-pulse-introduction.htm
https://community.sisense.com/t5/troubleshooting/pulse-troubleshooting-windows/ta-p/9589
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.
