Client-managed Qlik Sense
Butler can send notifications to various destinations when a reload task fails, succeeds, or is aborted in client-managed Qlik Sense.
A comparison of the different destinations is available in the setup documentation.
Alert Destinations
Butler supports several notification channels for reload task notifications in client-managed Qlik Sense:
Email Notifications
- Alert Emails - Comprehensive HTML email alerts with script logs and custom formatting
Messaging Platforms
- Slack & Teams Alerts - Rich formatted messages to Slack channels and Microsoft Teams
Incident Management
- New Relic - Send alerts to New Relic for incident tracking and analysis
- Signl4 - Mobile-first incident management with escalation policies
Data Storage & Analytics
- InfluxDB - Store failed reload metrics for trending and analysis
- MQTT - Publish alerts to MQTT brokers for IoT integration
- Webhooks - Send HTTP callbacks to custom endpoints
File System
- Failed Logs Storage - Automatically save failed reload script logs to disk for analysis
Key Features
The exact data sent to each destination varies, with the general features being:
- Rich Context: Include app metadata, error details, and script log excerpts
- Custom Templates: Handlebars-based templating for personalized alert content
- Selective Alerting: Configure alerts for specific tasks, apps, or environments
- Multi-Channel: Send the same alert to multiple destinations simultaneously
- Rate Limiting: Prevent alert flooding with configurable thresholds
Configuration Overview
Alert destinations can be configured with:
- Trigger Conditions: When to send alerts (failed, aborted, succeeded)
- Content Formatting: What information to include in alerts
- Recipient Targeting: Who should receive alerts for different scenarios
- Delivery Options: How and when alerts are delivered
For detailed configuration instructions, see the setup documentation.