...

ptarmiganlabs · Jan 10, 2024 · c20e03e · c20e03e
1 parent 4fbe656
commit c20e03e
Show file tree

Hide file tree

Showing 7 changed files with 41 additions and 8 deletions.
diff --git a/content/en/docs/examples/when things dont work/_index.md b/content/en/docs/examples/when things dont work/_index.md
@@ -76,7 +76,7 @@ Things to check:
       `TASKFAILURE: UDP server listening on 10.11.12.13:9998`
     - If there is a problem with the UDP server, the log might show a message like this (in this case the IP address is not valid for the Butler host):  
       `TASKFAILURE: Error in UDP error handler: Error: getsockname EINVAL`
-  - Check the Butler log files.
+  - Check the Butler log files.  
     When Butler receives a reload task event from Qlik Sense, it will check if rate limiting conditions are met, and also log a message about that.
     If there are no such messages:
     - Butler has not received the event from Qlik Sense.
@@ -94,3 +94,6 @@ Things to check:
   - If events arrive more frequently than the rate limiting settings allow, Butler will not forward all events.
     A failed rate limiting check will result in a log warning:  
     `Rate limiting failed. Not sending reload notification email for task ...`
+- Are alerts forwarded to some destination, but not others?
+  - Each destination can be enabled/disabled individually in the Butler configuration file.  
+    Make sure the destination you are interested in is enabled.
diff --git a/docs/docs/_print/index.html b/docs/docs/_print/index.html
@@ -11647,7 +11647,7 @@ <h3 id="failed-reload-alerts-not-working">Failed reload alerts not working</h3>
 <code>TASKFAILURE: Error in UDP error handler: Error: getsockname EINVAL</code></li>
 </ul>
 </li>
-<li>Check the Butler log files.
+<li>Check the Butler log files.<br>
 When Butler receives a reload task event from Qlik Sense, it will check if rate limiting conditions are met, and also log a message about that.
 If there are no such messages:
 <ul>
@@ -11676,6 +11676,12 @@ <h3 id="failed-reload-alerts-not-working">Failed reload alerts not working</h3>
 <code>Rate limiting failed. Not sending reload notification email for task ...</code></li>
 </ul>
 </li>
+<li>Are alerts forwarded to some destination, but not others?
+<ul>
+<li>Each destination can be enabled/disabled individually in the Butler configuration file.<br>
+Make sure the destination you are interested in is enabled.</li>
+</ul>
+</li>
 </ul>
 
 </div>

diff --git a/docs/docs/examples/_print/index.html b/docs/docs/examples/_print/index.html
@@ -2500,7 +2500,7 @@ <h3 id="failed-reload-alerts-not-working">Failed reload alerts not working</h3>
 <code>TASKFAILURE: Error in UDP error handler: Error: getsockname EINVAL</code></li>
 </ul>
 </li>
-<li>Check the Butler log files.
+<li>Check the Butler log files.<br>
 When Butler receives a reload task event from Qlik Sense, it will check if rate limiting conditions are met, and also log a message about that.
 If there are no such messages:
 <ul>
@@ -2529,6 +2529,12 @@ <h3 id="failed-reload-alerts-not-working">Failed reload alerts not working</h3>
 <code>Rate limiting failed. Not sending reload notification email for task ...</code></li>
 </ul>
 </li>
+<li>Are alerts forwarded to some destination, but not others?
+<ul>
+<li>Each destination can be enabled/disabled individually in the Butler configuration file.<br>
+Make sure the destination you are interested in is enabled.</li>
+</ul>
+</li>
 </ul>
 
 </div>

diff --git a/docs/docs/examples/index.xml b/docs/docs/examples/index.xml
@@ -936,7 +936,7 @@ If the rate limiting condition is met, this will be shown as &amp;ldquo;Rate lim
 &lt;code&gt;TASKFAILURE: Error in UDP error handler: Error: getsockname EINVAL&lt;/code&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
-&lt;li&gt;Check the Butler log files.
+&lt;li&gt;Check the Butler log files.&lt;br&gt;
 When Butler receives a reload task event from Qlik Sense, it will check if rate limiting conditions are met, and also log a message about that.
 If there are no such messages:
 &lt;ul&gt;
@@ -965,6 +965,12 @@ A failed rate limiting check will result in a log warning:&lt;br&gt;
 &lt;code&gt;Rate limiting failed. Not sending reload notification email for task ...&lt;/code&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
+&lt;li&gt;Are alerts forwarded to some destination, but not others?
+&lt;ul&gt;
+&lt;li&gt;Each destination can be enabled/disabled individually in the Butler configuration file.&lt;br&gt;
+Make sure the destination you are interested in is enabled.&lt;/li&gt;
+&lt;/ul&gt;
+&lt;/li&gt;
 &lt;/ul&gt;
 
       </description>

diff --git a/docs/docs/examples/when-things-dont-work/_print/index.html b/docs/docs/examples/when-things-dont-work/_print/index.html
@@ -167,7 +167,7 @@ <h3 id="failed-reload-alerts-not-working">Failed reload alerts not working</h3>
 <code>TASKFAILURE: Error in UDP error handler: Error: getsockname EINVAL</code></li>
 </ul>
 </li>
-<li>Check the Butler log files.
+<li>Check the Butler log files.<br>
 When Butler receives a reload task event from Qlik Sense, it will check if rate limiting conditions are met, and also log a message about that.
 If there are no such messages:
 <ul>
@@ -196,6 +196,12 @@ <h3 id="failed-reload-alerts-not-working">Failed reload alerts not working</h3>
 <code>Rate limiting failed. Not sending reload notification email for task ...</code></li>
 </ul>
 </li>
+<li>Are alerts forwarded to some destination, but not others?
+<ul>
+<li>Each destination can be enabled/disabled individually in the Butler configuration file.<br>
+Make sure the destination you are interested in is enabled.</li>
+</ul>
+</li>
 </ul>
 
 </div>

diff --git a/docs/docs/examples/when-things-dont-work/index.html b/docs/docs/examples/when-things-dont-work/index.html
@@ -508,7 +508,7 @@ <h3 id="failed-reload-alerts-not-working">Failed reload alerts not working</h3>
 <code>TASKFAILURE: Error in UDP error handler: Error: getsockname EINVAL</code></li>
 </ul>
 </li>
-<li>Check the Butler log files.
+<li>Check the Butler log files.<br>
 When Butler receives a reload task event from Qlik Sense, it will check if rate limiting conditions are met, and also log a message about that.
 If there are no such messages:
 <ul>
@@ -537,6 +537,12 @@ <h3 id="failed-reload-alerts-not-working">Failed reload alerts not working</h3>
 <code>Rate limiting failed. Not sending reload notification email for task ...</code></li>
 </ul>
 </li>
+<li>Are alerts forwarded to some destination, but not others?
+<ul>
+<li>Each destination can be enabled/disabled individually in the Butler configuration file.<br>
+Make sure the destination you are interested in is enabled.</li>
+</ul>
+</li>
 </ul>
 
         <div class="section-index">
@@ -554,7 +560,7 @@ <h3 id="failed-reload-alerts-not-working">Failed reload alerts not working</h3>
 
 
 	<div class="text-muted mt-5 pt-3 border-top">
-  Last modified 2024-01-10: <a href="https://github.com/google/docsy-example/commit/5aead1910ca1422f9afe6813c088dce240601e68">Add when-things-do-not-work section (5aead19)</a>
+  Last modified 2024-01-10: <a href="https://github.com/google/docsy-example/commit/4fbe65698913e4a4f2289db4086edd06f1f24723">Add info to things-do-not-work page (4fbe656)</a>
 </div>
 
 </div>

diff --git a/docs/sitemap.xml b/docs/sitemap.xml
@@ -318,7 +318,7 @@
     <lastmod>2023-12-15T15:31:42+01:00</lastmod>
   </url><url>
     <loc>https://butler.ptarmiganlabs.com/docs/examples/when-things-dont-work/</loc>
-    <lastmod>2024-01-10T07:45:08+01:00</lastmod>
+    <lastmod>2024-01-10T08:51:53+01:00</lastmod>
   </url><url>
     <loc>https://butler.ptarmiganlabs.com/blog/2023/04/14/butler-blog-moved-to-ptarmiganlabs.com/</loc>
     <lastmod>2023-04-14T10:18:33+02:00</lastmod>