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.
API endpoints can be individually enabled/disabled. 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’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.
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 its logfiles how long it’s been running and how much memory it uses. Optionally the memory usage can also be stored to an InfluxDB database, for later viewing/alerting in for example a Grafana dashboard.
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 couple of data connections first.
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.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.