deploy: 876df63

en/implementation-guide/trouble-shooting/index.html

@@ -1453,6 +1453,107 @@
       </ul>
     </nav>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#i-found-that-the-opensearch-data-nodes-disk-space-was-full-and-then-executed-delete-index_prefix-from-the-dev-tools-in-the-opensearch-dashboards-after-execution-the-index-name-suffix-no-longer-contains-the-time-format-what-should-i-do-to-fix" class="md-nav__link">
+    I found that the OpenSearch data node's disk space was full, and then executed "delete index_prefix*" from the dev tools in the OpenSearch Dashboards. After execution, the index name suffix no longer contains the time format. What should I do to fix？
+  </a>
+
+</li>
+
+        <li class="md-nav__item">
+  <a href="#standard-operating-procedure-for-proxy-stack-connection-problems" class="md-nav__link">
+    Standard Operating Procedure for Proxy Stack Connection Problems
+  </a>
+
+    <nav class="md-nav" aria-label="Standard Operating Procedure for Proxy Stack Connection Problems">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#when-i-access-opensearch-dashboards-through-the-proxy-the-browser-shows-504-gateway-timeout" class="md-nav__link">
+    When I access OpenSearch dashboards through the proxy, the browser shows 504 gateway timeout
+  </a>
+
+    <nav class="md-nav" aria-label="When I access OpenSearch dashboards through the proxy, the browser shows 504 gateway timeout">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#possible-root-cause" class="md-nav__link">
+    Possible Root cause:
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
+</li>
+
+          <li class="md-nav__item">
+  <a href="#when-i-access-opensearch-dashboards-through-the-proxy-the-browser-shows-site-cant-be-reached" class="md-nav__link">
+    When I access OpenSearch dashboards through the proxy, the browser shows "Site can't be reached"
+  </a>
+
+    <nav class="md-nav" aria-label="When I access OpenSearch dashboards through the proxy, the browser shows "Site can't be reached"">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#possible-root-cause_1" class="md-nav__link">
+    Possible root cause:
+  </a>
+
+</li>
+
+          <li class="md-nav__item">
+  <a href="#solution" class="md-nav__link">
+    Solution:
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
+</li>
+
+      </ul>
+    </nav>
+
+</li>
+
+        <li class="md-nav__item">
+  <a href="#i-set-the-log-collection-path-to-log_pathlog-what-will-be-the-impact" class="md-nav__link">
+    I set the log collection path to /log_path/*.log, what will be the impact?
+  </a>
+
+</li>
+
+        <li class="md-nav__item">
+  <a href="#the-log-file-names-are-the-same-for-different-systems-but-the-log-path-contains-the-system-name-in-order-to-differentiate-between-the-different-systems-i-wish-to-create-a-pipeline-to-handle-this-how-should-i-set-the-log-path" class="md-nav__link">
+    The log file names are the same for different systems, but the log path contains the system name in order to differentiate between the different systems. I wish to create a pipeline to handle this, how should I set the log path？
+  </a>
+
+    <nav class="md-nav" aria-label="The log file names are the same for different systems, but the log path contains the system name in order to differentiate between the different systems. I wish to create a pipeline to handle this, how should I set the log path？">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#lets-go-through-an-example" class="md-nav__link">
+    Let's go through an example:
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
+</li>
+
+        <li class="md-nav__item">
+  <a href="#in-eks-environment-i-am-using-daemonset-mode-to-collect-logs-but-my-logs-are-not-using-standard-output-mode-how-should-i-configure-the-yaml-file-for-deployment" class="md-nav__link">
+    In EKS environment, I am using DaemonSet mode to collect logs, but my logs are not using standard output mode, how should I configure the Yaml file for deployment?
+  </a>
+
 </li>
 
     </ul>
@@ -1745,6 +1846,107 @@
       </ul>
     </nav>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#i-found-that-the-opensearch-data-nodes-disk-space-was-full-and-then-executed-delete-index_prefix-from-the-dev-tools-in-the-opensearch-dashboards-after-execution-the-index-name-suffix-no-longer-contains-the-time-format-what-should-i-do-to-fix" class="md-nav__link">
+    I found that the OpenSearch data node's disk space was full, and then executed "delete index_prefix*" from the dev tools in the OpenSearch Dashboards. After execution, the index name suffix no longer contains the time format. What should I do to fix？
+  </a>
+
+</li>
+
+        <li class="md-nav__item">
+  <a href="#standard-operating-procedure-for-proxy-stack-connection-problems" class="md-nav__link">
+    Standard Operating Procedure for Proxy Stack Connection Problems
+  </a>
+
+    <nav class="md-nav" aria-label="Standard Operating Procedure for Proxy Stack Connection Problems">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#when-i-access-opensearch-dashboards-through-the-proxy-the-browser-shows-504-gateway-timeout" class="md-nav__link">
+    When I access OpenSearch dashboards through the proxy, the browser shows 504 gateway timeout
+  </a>
+
+    <nav class="md-nav" aria-label="When I access OpenSearch dashboards through the proxy, the browser shows 504 gateway timeout">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#possible-root-cause" class="md-nav__link">
+    Possible Root cause:
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
+</li>
+
+          <li class="md-nav__item">
+  <a href="#when-i-access-opensearch-dashboards-through-the-proxy-the-browser-shows-site-cant-be-reached" class="md-nav__link">
+    When I access OpenSearch dashboards through the proxy, the browser shows "Site can't be reached"
+  </a>
+
+    <nav class="md-nav" aria-label="When I access OpenSearch dashboards through the proxy, the browser shows "Site can't be reached"">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#possible-root-cause_1" class="md-nav__link">
+    Possible root cause:
+  </a>
+
+</li>
+
+          <li class="md-nav__item">
+  <a href="#solution" class="md-nav__link">
+    Solution:
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
+</li>
+
+      </ul>
+    </nav>
+
+</li>
+
+        <li class="md-nav__item">
+  <a href="#i-set-the-log-collection-path-to-log_pathlog-what-will-be-the-impact" class="md-nav__link">
+    I set the log collection path to /log_path/*.log, what will be the impact?
+  </a>
+
+</li>
+
+        <li class="md-nav__item">
+  <a href="#the-log-file-names-are-the-same-for-different-systems-but-the-log-path-contains-the-system-name-in-order-to-differentiate-between-the-different-systems-i-wish-to-create-a-pipeline-to-handle-this-how-should-i-set-the-log-path" class="md-nav__link">
+    The log file names are the same for different systems, but the log path contains the system name in order to differentiate between the different systems. I wish to create a pipeline to handle this, how should I set the log path？
+  </a>
+
+    <nav class="md-nav" aria-label="The log file names are the same for different systems, but the log path contains the system name in order to differentiate between the different systems. I wish to create a pipeline to handle this, how should I set the log path？">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#lets-go-through-an-example" class="md-nav__link">
+    Let's go through an example:
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
+</li>
+
+        <li class="md-nav__item">
+  <a href="#in-eks-environment-i-am-using-daemonset-mode-to-collect-logs-but-my-logs-are-not-using-standard-output-mode-how-should-i-configure-the-yaml-file-for-deployment" class="md-nav__link">
+    In EKS environment, I am using DaemonSet mode to collect logs, but my logs are not using standard output mode, how should I configure the Yaml file for deployment?
+  </a>
+
 </li>
 
     </ul>
@@ -1918,6 +2120,80 @@ <h4 id="amazon-linux-2023">Amazon Linux 2023</h4>
 echo /usr/local/openssl11/lib/ &gt;&gt; /etc/ld.so.conf
 ldconfig
 </code></pre></div>
+<h2 id="i-found-that-the-opensearch-data-nodes-disk-space-was-full-and-then-executed-delete-index_prefix-from-the-dev-tools-in-the-opensearch-dashboards-after-execution-the-index-name-suffix-no-longer-contains-the-time-format-what-should-i-do-to-fix">I found that the OpenSearch data node's disk space was full, and then executed "delete index_prefix*" from the dev tools in the OpenSearch Dashboards. After execution, the index name suffix no longer contains the time format. What should I do to fix？</h2>
+<div class="admonition warning">
+<p class="admonition-title">Note</p>
+<p>The following operation will delete the currently written index, resulting in data loss.</p>
+</div>
+<ol>
+<li>Open the Centralized Logging with OpenSearch console, find the pipeline which has this issue and choose <strong>View details</strong>.</li>
+<li>Go to Monitoring &gt; Lambda Processor, and click on the link(start with <code>/aws/lambda/CL-xxx</code>) under <strong>Lambda Processor</strong>.</li>
+</ol>
+<p><img alt="" src="../../images/trouble-shooting/lambda-link.png" /></p>
+<ol>
+<li>Go to <strong>Lambda</strong> console &gt; <strong>Configuration</strong> &gt; <strong>Concurrency</strong>, choose <strong>Edit</strong>, select <strong>Reserve concurrency</strong> and set it to 0.</li>
+</ol>
+<p><img alt="" src="../../images/trouble-shooting/lambda-configuration-concurrency.png" /></p>
+<p><img alt="" src="../../images/trouble-shooting/lambda-edit-concurrency.png" /></p>
+<ol>
+<li>Open the OpenSearch Dashboards, go to <strong>Dev Tools</strong>, input <code>DELETE your_index_name</code> and click to send request.</li>
+</ol>
+<p><img alt="" src="../../images/trouble-shooting/aos-dev-tools.png" /></p>
+<p><img alt="" src="../../images/trouble-shooting/delete_index.png" /></p>
+<ol>
+<li>Input <code>GET _cat/indices/your_index_name</code> and click to send request. If <strong>"status"</strong> is 404 and <strong>"type"</strong> is index_not_found_exception in the returned result, it means success. Otherwise, please repeat step 4.</li>
+</ol>
+<p><img alt="" src="../../images/trouble-shooting/cat_index.png" /></p>
+<ol>
+<li>
+<p>Input <code>POST /your_index_name/_rollover</code> and click to send request.</p>
+</li>
+<li>
+<p>Go to <strong>Lambda</strong> console &gt; <strong>Configuration</strong> &gt; <strong>Concurrency</strong>, choose <strong>Edit</strong>, select <strong>Reserve concurrency</strong> and set it to the value you want, or select <strong>Use unreserved account concurrency</strong>, save.</p>
+</li>
+</ol>
+<h2 id="standard-operating-procedure-for-proxy-stack-connection-problems">Standard Operating Procedure for Proxy Stack Connection Problems</h2>
+<h3 id="when-i-access-opensearch-dashboards-through-the-proxy-the-browser-shows-504-gateway-timeout">When I access OpenSearch dashboards through the proxy, the browser shows 504 gateway timeout</h3>
+<h5 id="possible-root-cause">Possible Root cause:</h5>
+<p>a. If instances keeps terminating and initializing</p>
+<pre><code>  i. Wrong security Group
+</code></pre>
+<p>b. Instances are not keep terminating</p>
+<pre><code>  i. VPC peering request not accepted
+
+  ii. Peering with the wrong VPC
+
+  iii. Route table has the wrong routes
+</code></pre>
+<p>c. Check if VPC Peering is working.</p>
+<h3 id="when-i-access-opensearch-dashboards-through-the-proxy-the-browser-shows-site-cant-be-reached">When I access OpenSearch dashboards through the proxy, the browser shows "Site can't be reached"</h3>
+<p><img alt="" src="../../images/trouble-shooting/site_cannt_be_reached.png" /></p>
+<h5 id="possible-root-cause_1">Possible root cause:</h5>
+<pre><code>1. Application Load Balancer is deployed inside private subnet
+
+2. The proxy stack has just been re-deployed, it takes at least 15mins for DNS server to resolve the new Load Balancer endpoint address
+</code></pre>
+<h5 id="solution">Solution:</h5>
+<pre><code>1. ALB deploy location is wrong, just delete the proxy stack and create a new one
+
+2. wait for 15 mins
+</code></pre>
+<h2 id="i-set-the-log-collection-path-to-log_pathlog-what-will-be-the-impact">I set the log collection path to /log_path/*.log, what will be the impact?</h2>
+<div class="admonition warning">
+<p class="admonition-title">Note</p>
+<p>Normally we don't recommend using wildcard * as a prefix for matching logs. If there are hundreds, or even thousands of files in the directory, this will seriously affect the rate of FluentBit's log collection, and it is recommended that you can remove outdated files on a regular basis.</p>
+</div>
+<h2 id="the-log-file-names-are-the-same-for-different-systems-but-the-log-path-contains-the-system-name-in-order-to-differentiate-between-the-different-systems-i-wish-to-create-a-pipeline-to-handle-this-how-should-i-set-the-log-path">The log file names are the same for different systems, but the log path contains the system name in order to differentiate between the different systems. I wish to create a pipeline to handle this, how should I set the log path？</h2>
+<div class="admonition info">
+<p class="admonition-title">Note</p>
+<h4 id="lets-go-through-an-example">Let's go through an example:</h4>
+<p>For example, we have 3 environments, dev, staging, prod. The log paths are /log_path/dev/jvm.log, /log_path/staging/jvm.log, and /log_path/prod/jvm.log. In this scenario if you wish to create only one pipeline, you can set the log path as follows:</p>
+<p><img alt="" src="../../images/trouble-shooting/log_path.png" /></p>
+<p><code>/log_path/*/jvm.log</code>.</p>
+</div>
+<h2 id="in-eks-environment-i-am-using-daemonset-mode-to-collect-logs-but-my-logs-are-not-using-standard-output-mode-how-should-i-configure-the-yaml-file-for-deployment">In EKS environment, I am using DaemonSet mode to collect logs, but my logs are not using standard output mode, how should I configure the Yaml file for deployment?</h2>
+<p>As we know, if you create a pipeline and the selected log source is EKS in the CLO, the system will automatically generate the content in YAML format for you to assist you in creating the deployment file for you to deploy FluentBit. You can match the log path <code>/your_log_path/</code> in the YAML file and remove the <code>Parser              cri_regex</code>. Please refer to the following screenshot for details:</p>
+<p><img alt="" src="../../images/trouble-shooting/without_cri_log.png" /></p>