Concepts

Deep dive into the various components that make up Butler.

Key-value store

Overview of the key-value database concept and how it is imlpemented in Butler.

Scheduler

The how and why of the Butler scheduler.

Failed/aborted reloads

Overview of the actions Butler can take when a reload task fails or is aborted.

Successful reloads

Tracking successful reloads can be useful for various reasons, for example knowing how long different app reloads takes on average.

Starting Sense tasks in style

Starting Sense reload tasks (and other tasks) is usually done from the QMC.
Using Butler’s REST API it’s however very easy to start tasks from any third party system capable of making a REST call.

Incident management tools

There are various enterprise grade tools for handling IT incidents. Butler can integrate with such tools, for example forwarding information about failed reloads to an IT operations team.

File system access: copy/move/delete files

Manipulating files from Sense load scripts in a secure yet flexible way.

MQTT integration

Details about how Qlik Sense can use Butler to send pub-sub messages using MQTT.

UDP client

A basic, stand-alone UDP client is included in Butler.

Monitor Windows services

Butler can monitor Windows services and send alerts if a service is not running.
Services on multiple servers can be monitored, and Butler can send alerts to destinations such as Slack, Teams, email, webhooks, InfluxDB, New Relic and MQTT.

Real-time metrics

Details about the real-time metrics (active user count etc) provided by Butler.

Last modified 2021-04-22: First commit (c105eb7)