---
@@ -5122,7 +5122,7 @@ What’s this?
MQTT is a light weight messaging protocol based on a publish-subscribe metaphore. It is widely used in the Internet of Things (IoT) and telecom sectors.
MQTT has features such as guaranteed delivery of messages, which makes it very useful for communicating between Sense and both up- and downstream source/destination systems.
Butler can be configured to forward events from Sense (reload task failures, aborted reload tasks, windows services starting/stopping, user session start/stop etc) as MQTT messages.
-Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.
+Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.
Defining what MQTT broker/server to connect to
Butler can use either of two kinds of MQTT brokers:
diff --git a/docs/docs/getting-started/setup/index.xml b/docs/docs/getting-started/setup/index.xml
index 64089af9..e69d2ee8 100644
--- a/docs/docs/getting-started/setup/index.xml
+++ b/docs/docs/getting-started/setup/index.xml
@@ -960,7 +960,7 @@ In such cases it’s a waste of resources to keep the license assigned t
<h2 id="how-it-works">How it works</h2>
<p>The data in the key-value store is <em>not</em> persisted to disk, which means that key-value data will be lost if Butler is restarted.<br>
This behaviour could possibly be changed if there is a need, please open a <a href="https://github.com/ptarmiganlabs/butler/issues">GitHub ticket</a> if key-value persistence is of interest.</p>
-<p>Key-value data is manipulated using Butler’s <a href="https://butler.ptarmiganlabs.com/docs/reference/rest-api/?operationsSorter=alpha">REST API</a>.</p>
+<p>Key-value data is manipulated using Butler’s <a href="https://butler.ptarmiganlabs.com/docs/reference/rest-api-1/?operationsSorter=alpha">REST API</a>.</p>
<p>The <a href="https://butler.ptarmiganlabs.com/docs/reference/key-value/">Reference docs</a> section has more information about the key-value store.</p>
<h2 id="settings-in-config-file">Settings in config file</h2>
<div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#000">---</span><span style="color:#f8f8f8;text-decoration:underline">
@@ -1063,7 +1063,7 @@ In QlikView this was possible, but also resulted in risks and potential attack v
<p><a href="https://mqtt.org/">MQTT</a> is a light weight messaging protocol based on a publish-subscribe metaphore. It is widely used in the Internet of Things (IoT) and telecom sectors.</p>
<p>MQTT has features such as guaranteed delivery of messages, which makes it very useful for communicating between Sense and both up- and downstream source/destination systems.</p>
<p>Butler can be configured to forward events from Sense (reload task failures, aborted reload tasks, windows services starting/stopping, user session start/stop etc) as MQTT messages.</p>
-<p>Butler’s <a href="https://butler.ptarmiganlabs.com/docs/reference/rest-api/?operationsSorter=alpha">REST API</a> also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.</p>
+<p>Butler’s <a href="https://butler.ptarmiganlabs.com/docs/reference/rest-api-1/?operationsSorter=alpha">REST API</a> also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.</p>
<h3 id="defining-what-mqtt-brokerserver-to-connect-to">Defining what MQTT broker/server to connect to</h3>
<p>Butler can use either of two kinds of MQTT brokers:</p>
<ol>
diff --git a/docs/docs/getting-started/setup/key-value-store/index.html b/docs/docs/getting-started/setup/key-value-store/index.html
index 9a3bd15e..80689723 100644
--- a/docs/docs/getting-started/setup/key-value-store/index.html
+++ b/docs/docs/getting-started/setup/key-value-store/index.html
@@ -465,7 +465,7 @@ What’s this?
How it works
The data in the key-value store is not persisted to disk, which means that key-value data will be lost if Butler is restarted.
This behaviour could possibly be changed if there is a need, please open a GitHub ticket if key-value persistence is of interest.
-Key-value data is manipulated using Butler’s REST API.
+Key-value data is manipulated using Butler’s REST API.
The Reference docs section has more information about the key-value store.
Settings in config file
---
diff --git a/docs/docs/getting-started/setup/key-value-store/printview/index.html b/docs/docs/getting-started/setup/key-value-store/printview/index.html
index 98841cb2..6abef631 100644
--- a/docs/docs/getting-started/setup/key-value-store/printview/index.html
+++ b/docs/docs/getting-started/setup/key-value-store/printview/index.html
@@ -115,7 +115,7 @@ What’s this?
How it works
The data in the key-value store is not persisted to disk, which means that key-value data will be lost if Butler is restarted.
This behaviour could possibly be changed if there is a need, please open a GitHub ticket if key-value persistence is of interest.
-Key-value data is manipulated using Butler’s REST API.
+Key-value data is manipulated using Butler’s REST API.
The Reference docs section has more information about the key-value store.
Settings in config file
---
diff --git a/docs/docs/getting-started/setup/mqtt/index.html b/docs/docs/getting-started/setup/mqtt/index.html
index 2e9735cb..8cff66d9 100644
--- a/docs/docs/getting-started/setup/mqtt/index.html
+++ b/docs/docs/getting-started/setup/mqtt/index.html
@@ -462,7 +462,7 @@ What’s this?
MQTT is a light weight messaging protocol based on a publish-subscribe metaphore. It is widely used in the Internet of Things (IoT) and telecom sectors.
MQTT has features such as guaranteed delivery of messages, which makes it very useful for communicating between Sense and both up- and downstream source/destination systems.
Butler can be configured to forward events from Sense (reload task failures, aborted reload tasks, windows services starting/stopping, user session start/stop etc) as MQTT messages.
-Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.
+Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.
Defining what MQTT broker/server to connect to
Butler can use either of two kinds of MQTT brokers:
diff --git a/docs/docs/getting-started/setup/mqtt/printview/index.html b/docs/docs/getting-started/setup/mqtt/printview/index.html
index fcf58a04..e97c3017 100644
--- a/docs/docs/getting-started/setup/mqtt/printview/index.html
+++ b/docs/docs/getting-started/setup/mqtt/printview/index.html
@@ -108,7 +108,7 @@ What’s this?
MQTT is a light weight messaging protocol based on a publish-subscribe metaphore. It is widely used in the Internet of Things (IoT) and telecom sectors.
MQTT has features such as guaranteed delivery of messages, which makes it very useful for communicating between Sense and both up- and downstream source/destination systems.
Butler can be configured to forward events from Sense (reload task failures, aborted reload tasks, windows services starting/stopping, user session start/stop etc) as MQTT messages.
-Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.
+Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.
Defining what MQTT broker/server to connect to
Butler can use either of two kinds of MQTT brokers:
diff --git a/docs/docs/getting-started/setup/printview/index.html b/docs/docs/getting-started/setup/printview/index.html
index a9600d9b..6b3c56c8 100644
--- a/docs/docs/getting-started/setup/printview/index.html
+++ b/docs/docs/getting-started/setup/printview/index.html
@@ -3877,7 +3877,7 @@ What’s this?
How it works
The data in the key-value store is not persisted to disk, which means that key-value data will be lost if Butler is restarted.
This behaviour could possibly be changed if there is a need, please open a GitHub ticket if key-value persistence is of interest.
-Key-value data is manipulated using Butler’s REST API.
+Key-value data is manipulated using Butler’s REST API.
The Reference docs section has more information about the key-value store.
Settings in config file
---
@@ -4437,7 +4437,7 @@ What’s this?
MQTT is a light weight messaging protocol based on a publish-subscribe metaphore. It is widely used in the Internet of Things (IoT) and telecom sectors.
MQTT has features such as guaranteed delivery of messages, which makes it very useful for communicating between Sense and both up- and downstream source/destination systems.
Butler can be configured to forward events from Sense (reload task failures, aborted reload tasks, windows services starting/stopping, user session start/stop etc) as MQTT messages.
-Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.
+Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.
Defining what MQTT broker/server to connect to
Butler can use either of two kinds of MQTT brokers:
diff --git a/docs/docs/index.html b/docs/docs/index.html
index fc720781..a3860358 100644
--- a/docs/docs/index.html
+++ b/docs/docs/index.html
@@ -1051,7 +1051,7 @@
diff --git a/docs/docs/index.xml b/docs/docs/index.xml
index 8a590431..40256796 100644
--- a/docs/docs/index.xml
+++ b/docs/docs/index.xml
@@ -715,8 +715,8 @@ Here’s a list of features that are candidates for removal from Butler,
For example, when Butler was started it wouldn’t capture currently active users or sessions - it was only after some event captured in the logs that Butler would update it’s internal counters. This meant that it would take some time (sometimes quite long) until the metrics were even approaching the real number of users using Sense.</p>
<p>There was also the risk of Butler missing UDP messages and not registering the associated log event.</p>
<p>The affected API endpoints are:</p>
-<p><a href="https://butler.ptarmiganlabs.com/docs/reference/rest-api/?operationsSorter=alpha">/v4/activeusercount</a><br>
-<a href="https://butler.ptarmiganlabs.com/docs/reference/rest-api/?operationsSorter=alpha">/v4/activeusers</a></p>
+<p><a href="https://butler.ptarmiganlabs.com/docs/reference/rest-api-1/?operationsSorter=alpha">/v4/activeusercount</a><br>
+<a href="https://butler.ptarmiganlabs.com/docs/reference/rest-api-1/?operationsSorter=alpha">/v4/activeusers</a></p>
<div class="alert alert-info" role="alert">
diff --git a/docs/docs/printview/index.html b/docs/docs/printview/index.html
index b42dd2a6..10de4452 100644
--- a/docs/docs/printview/index.html
+++ b/docs/docs/printview/index.html
@@ -2772,7 +2772,7 @@ Create directories, copy/move/d
More info here.
Exporting apps as JSON can be very useful for backup purposes. Doing regular snapshots of all apps in a Sense cluster is a fast and space-effective way of keeping point-in-time backups.
-The REST API documentation has full docs for the /v4/app/{appId}/dump
endpoint.
+The REST API documentation has full docs for the /v4/app/{appId}/dump
endpoint.
Easily post messages to Slack
Slack messages can include full formatting (web links, text formatting etc), as well as “poking” users.
I.e. notifying specific Slack users that they have a new message.
@@ -2818,8 +2818,8 @@ Real-time metrics around active u
For example, when Butler was started it wouldn’t capture currently active users or sessions - it was only after some event captured in the logs that Butler would update it’s internal counters. This meant that it would take some time (sometimes quite long) until the metrics were even approaching the real number of users using Sense.
There was also the risk of Butler missing UDP messages and not registering the associated log event.
The affected API endpoints are:
-/v4/activeusercount
-/v4/activeusers
+/v4/activeusercount
+/v4/activeusers
@@ -6882,7 +6882,7 @@
What’s this?
How it works
The data in the key-value store is not persisted to disk, which means that key-value data will be lost if Butler is restarted.
This behaviour could possibly be changed if there is a need, please open a GitHub ticket if key-value persistence is of interest.
-
Key-value data is manipulated using Butler’s REST API.
+
Key-value data is manipulated using Butler’s REST API.
The Reference docs section has more information about the key-value store.
Settings in config file
---
@@ -7442,7 +7442,7 @@ What’s this?
MQTT is a light weight messaging protocol based on a publish-subscribe metaphore. It is widely used in the Internet of Things (IoT) and telecom sectors.
MQTT has features such as guaranteed delivery of messages, which makes it very useful for communicating between Sense and both up- and downstream source/destination systems.
Butler can be configured to forward events from Sense (reload task failures, aborted reload tasks, windows services starting/stopping, user session start/stop etc) as MQTT messages.
-Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.
+Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from Sense apps’ load scripts.
Defining what MQTT broker/server to connect to
Butler can use either of two kinds of MQTT brokers:
@@ -9733,7 +9733,7 @@ Butl
For example, you might have a QVD folder at e:\data\qvd\sales\temp
.
You also need to remove old QVDs from that folder.
This could be done with scheduled BAT/CMD files or PowerShell scripts, but it might be better/more flexible/easier/preferred to do this cleanup from the load script of a Sense app.
-The solution: Add e:\data\qvd\sales\temp
to Butler’s list of folders in which files can be deleted, then call Butler’s /v4/filedelete
API endpoint from within your app’s load script. Done!
+The solution: Add e:\data\qvd\sales\temp
to Butler’s list of folders in which files can be deleted, then call Butler’s /v4/filedelete
API endpoint from within your app’s load script. Done!
Convenience subs
Butler includes a set of Subs that make it easy to use the file copy/move/delete APIs.
These subs are found in this .qvs file as well as embedded in the Butler demo app.
@@ -11978,7 +11978,7 @@ 4.7.2 - Partial loads in Qlik Sense
Butler has an API for doing partial reloads of apps. A couple of demo apps are also includedin the GitHub repository.
Partial reload API
-
The full API documentation is available in the Reference section, here we’re interested in the PUT /v4/app/{appId}/reload
endpoint.
+
The full API documentation is available in the Reference section, here we’re interested in the PUT /v4/app/{appId}/reload
endpoint.
Demo apps for partial reloads
A couple of apps showing how to use Butler’s partial load API are included in the GitHub repository.
@@ -14334,7 +14334,7 @@ Manual vs API created schedules
5.5 - Key-value store
Details about the Butler key-value store.
Key-value store overview
-The API documentation is the best, most complete source of information about the key-value API endpoints.
+The API documentation is the best, most complete source of information about the key-value API endpoints.
Namespaces
Each key-value pair is associated with a “namespace”, which is simply a way to group KV pairs together in logical groups.
Examples:
diff --git a/docs/docs/reference/index.xml b/docs/docs/reference/index.xml
index 3afceed1..04eee9c0 100644
--- a/docs/docs/reference/index.xml
+++ b/docs/docs/reference/index.xml
@@ -1987,7 +1987,7 @@ On the other hand, it’s questionable if Sense jobs should run more oft
<h2 id="key-value-store-overview">Key-value store overview</h2>
-<p>The <a href="https://butler.ptarmiganlabs.com/docs/reference/rest-api/?operationsSorter=alpha">API documentation</a> is the best, most complete source of information about the key-value API endpoints.</p>
+<p>The <a href="https://butler.ptarmiganlabs.com/docs/reference/rest-api-1/?operationsSorter=alpha">API documentation</a> is the best, most complete source of information about the key-value API endpoints.</p>
<h2 id="namespaces">Namespaces</h2>
<p>Each key-value pair is associated with a “namespace”, which is simply a way to group KV pairs together in logical groups.</p>
<p>Examples:</p>
diff --git a/docs/docs/reference/key-value/index.html b/docs/docs/reference/key-value/index.html
index e9ff6bc0..d45d3ccc 100644
--- a/docs/docs/reference/key-value/index.html
+++ b/docs/docs/reference/key-value/index.html
@@ -452,7 +452,7 @@ Key-value store
Key-value store overview
-The API documentation is the best, most complete source of information about the key-value API endpoints.
+The API documentation is the best, most complete source of information about the key-value API endpoints.
Namespaces
Each key-value pair is associated with a “namespace”, which is simply a way to group KV pairs together in logical groups.
Examples:
diff --git a/docs/docs/reference/key-value/printview/index.html b/docs/docs/reference/key-value/printview/index.html
index 8fb28aef..f7bdc20b 100644
--- a/docs/docs/reference/key-value/printview/index.html
+++ b/docs/docs/reference/key-value/printview/index.html
@@ -105,7 +105,7 @@ Key-value store
Key-value store overview
-
The API documentation is the best, most complete source of information about the key-value API endpoints.
+
The API documentation is the best, most complete source of information about the key-value API endpoints.
Namespaces
Each key-value pair is associated with a “namespace”, which is simply a way to group KV pairs together in logical groups.
Examples:
diff --git a/docs/docs/reference/printview/index.html b/docs/docs/reference/printview/index.html
index 29adcb07..a32d7aa9 100644
--- a/docs/docs/reference/printview/index.html
+++ b/docs/docs/reference/printview/index.html
@@ -2371,7 +2371,7 @@
Manual vs API created schedules
5 - Key-value store
Details about the Butler key-value store.
Key-value store overview
-
The API documentation is the best, most complete source of information about the key-value API endpoints.
+
The API documentation is the best, most complete source of information about the key-value API endpoints.
Namespaces
Each key-value pair is associated with a “namespace”, which is simply a way to group KV pairs together in logical groups.
Examples:
diff --git a/docs/sitemap.xml b/docs/sitemap.xml
index 20146c7a..09901615 100644
--- a/docs/sitemap.xml
+++ b/docs/sitemap.xml
@@ -21,7 +21,7 @@
2023-06-13T15:01:58+02:00
https://butler.ptarmiganlabs.com/docs/concepts/key-value/
- 2021-04-22T21:58:55+02:00
+ 2024-04-15T12:16:15+02:00
https://butler.ptarmiganlabs.com/docs/concepts/incident-mgmt-tools/new-relic/
2022-06-21T09:33:35+02:00
@@ -66,7 +66,7 @@
2022-04-07T10:17:58+02:00
https://butler.ptarmiganlabs.com/docs/
- 2024-04-15T08:26:56+02:00
+ 2024-04-15T12:16:15+02:00
https://butler.ptarmiganlabs.com/docs/getting-started/
2021-04-22T21:58:55+02:00
@@ -93,7 +93,7 @@
2022-06-21T09:33:35+02:00
https://butler.ptarmiganlabs.com/docs/concepts/scheduler/
- 2021-04-22T21:58:55+02:00
+ 2024-04-15T12:16:15+02:00
https://butler.ptarmiganlabs.com/docs/getting-started/setup/qlik-sense-server-settings/
2023-06-13T15:01:58+02:00
@@ -336,7 +336,7 @@
2024-01-10T09:00:58+01:00
https://butler.ptarmiganlabs.com/
- 2024-04-15T10:38:49+02:00
+ 2024-04-15T12:16:15+02:00
https://butler.ptarmiganlabs.com/community/
2021-04-22T21:58:55+02:00