Which config file to use
Butler can use multiple config files. Here you learn to control which one is used by Butler.
Butler can use multiple config files. Here you learn to control which one is used by Butler.
Details on how to configure the connection from Butler to Qlik Sense Enterprise on Windows.
Butler’s REST API can be enabled/disabled in itself. If the API is enabled, individual API endpoints can then be enabled/disabled as needed. By only enabling the endpoints needed for your Qlik Sense environment, memory usage is minimised and security maximised.
Butler offers a lot of flexibility when it comes to alerts when reloads fail or are aborted.
Learn how to set up the desired features, the alert layout, formatting and more.
Butler can detect, capture and store all script logs of reload tasks that failed.
This makes it much easier to find and analyse the script logs of faile reloads.
Butler can monitor Windows services and alert if they are not running.
This is useful for monitoring services that are critical for Qlik Sense to function - or any other important service.
Messages can be sent when services stop or start, with message destinations such as Slack, Teams, email, New Relic, InfluxDB, webhooks and MQTT.
Butler can monitor and manage Qlik Sense user licenses.
Butler’s scheduler complements the Qlik Sense built-in scheduler with more flexible triggers and a devops friendly API/file format for storing scheduling data.
Butler contains a key-value store that is accessible via the REST API.
Butler contains REST API endpoints for moving, copying and deleting files.
There are various enterprise grade tools for handling IT incidents.
Butler can integrate with such tools, for example forwarding information about failed reloads.
Below you find instuctions for configuring the currently supported incident management tools.
Butler can use MQTT as a channel for pub-sub style M2M (machine to machine) messages. This page describes how to configure MQTT in Butler.
Heartbeats provide a way to monitor that Butler is running and working as intended.
Butler can send periodic heartbeat messages to a monitoring tool, which can then alert if Butler hasn’t checked in as expected.
Butler can optionally log to the console and its logfiles how long it’s been running and how much memory it uses.
Optionally the memory usage can also be stored to an external database for later viewing/alerting in for example a Grafana dashboard.
InfluxDB and New Relic are currently supported targets.
Docker has a concept of “health checks”, which is a way for Docker containers to tell the Docker runtime engine that the container is alive and well.
Butler can be configured to send such health check messages to Docker.
If you intend to call Butler’s REST API from the load script of Sense apps, you must create a few data connections first. A couple of them are mandatory, one is optional.
Butler can receive and act on any user event detected in the Sense log files. This page describes how to set this up using Sense log appenders.
Qlik Sense tasks can be started using Butler’s REST API.
Using the task filtering feature it’s possible to control which tasks can be started.
This can be useful for sysadmins when only a limited set of tasks should be available to third party systems.