title: Debugging Filebeat in the ELK stack
body: <p>I am having some issues with my ELK system.  The client-side work is as follows:</p>
  <p><strong>Filebeat -&gt; Logstash --&gt; Elastic --&gt; Kibana</strong></p>
  <p>Parts of our logs don't arrive to Elastic from specific machines.
  I suspect that the problem is in the log harvesting in Filebeat.</p>
  <p>I tried to find information on the debugging system on the Elastic and GitHub websites but I only found <a href="https://www.elastic.co/guide/en/beats/filebeat/current/command-line-options.html" rel="nofollow noreferrer">these</a> <a href="https://github.com/elastic/beats/issues/3264" rel="nofollow noreferrer">links</a>, which says:</p>
  <blockquote>
  <p>By default, Filebeat sends all its output to syslog. When you run
  Filebeat in the foreground, you can use the -e command line flag to
  redirect the output to standard error instead. For example:</p>
  <p><strong>filebeat -e</strong> The default configuration file is filebeat.yml (the
  location of the file varies by platform). You can use a different
  configuration file by specifying the -c flag. For example:</p>
  <p><strong>filebeat -e -c myfilebeatconfig.yml</strong></p>
  <p>You can increase the verbosity of
  debug messages by enabling one or more debug selectors. For example,
  to view the published transactions, you can start Filebeat with the
  publish selector like this:</p>
  <p><strong>filebeat -e -d &quot;publish&quot;</strong></p>
  <p>If you want all the debugging output (fair
  warning, it’s quite a lot), you can use *, like this:</p>
  <p><strong>filebeat -e -d &quot;*&quot;</strong></p>
  </blockquote>
  <p><code>filebeat -e</code> doesn't show me what I need, and the other options provide too much information.  Are there any other methods to debug our ELK with this specific architecture? Or are there any other command-line options?</p>
  <p>FYI: I already tried to set FileBeat service on my machine, where it performs great with the same <code>filebeat.yml</code> configuration.</p>