<p>After looking a bit further, I found it in the sample called <code>filebeat.full.yml</code></p>

<ul>
<li>So I added this section to the filebeat.yml</li>
<li>Restarted filebeat </li>
</ul>

<p>After running at 100% CPU for minute, Kibana is now immediately showing the results. That was easier than I expected.</p>

<pre><code>#==========================  Modules configuration ============================
filebeat.modules:

#------------------------------- Apache2 Module ------------------------------
- module: apache2
  # Access logs
  access:
    #enabled: true

    # Set custom paths for the log files. If left empty,
    # Filebeat will choose the paths depending on your OS.
    var.paths: ["MY-CUSTOM-PATH"]
</code></pre>

CC BY-SA 3.0
2017-04-08T05:02:59.307Z
2017-04-08T05:02:59.307Z
scipilot
<p>I am setting up the Elastic Filebeat beat for the first time.  I have followed the <a href="https://www.elastic.co/guide/en/beats/filebeat/5.3/filebeat-modules-quickstart.html" rel="nofollow noreferrer">guide here</a>, and have got the Apache2 filebeat module up and running, it's connected to my Elastic and the dashboards have arrived in Kibana. </p>

<p>Currently it's using the default path to read the Apache log files, but I want to point it to a different directory.</p>

<p>There is a setting <code>var.paths</code> <a href="https://www.elastic.co/guide/en/beats/filebeat/5.3/filebeat-module-apache2.html#_var_paths" rel="nofollow noreferrer">documented here</a> for this purpose, but I can't see where this setting is applied in the configuration for Filebeat.</p>

<p>I've looked through the Yaml files in the installation and can see the Apache2 module default config, but it doesn't look like I should modify that.</p>

<p>I'm guessing I should add something to the filebeat.yml, but there doesn't seem to be a placeholder for "modules.apache" or similar.</p>

<p>I'm trialling on MacOSX, will be deploying on Ubuntu, but I don't believe this to be a platform-specific question.</p>

<configuration><logstash>
Where is the apache2 filebeat module configured?
scipilot
# Where is the apache2 filebeat module configured?

(Asked by: username_0 on 2017-04-08)

I am setting up the Elastic Filebeat beat for the first time. I have followed the [guide here](https://www.elastic.co/guide/en/beats/filebeat/5.3/filebeat-modules-quickstart.html), and have got the Apache2 filebeat module up and running, it's connected to my Elastic and the dashboards have arrived in Kibana.

Currently it's using the default path to read the Apache log files, but I want to point it to a different directory.

There is a setting `var.paths` [documented here](https://www.elastic.co/guide/en/beats/filebeat/5.3/filebeat-module-apache2.html#_var_paths) for this purpose, but I can't see where this setting is applied in the configuration for Filebeat.

I've looked through the Yaml files in the installation and can see the Apache2 module default config, but it doesn't look like I should modify that.

I'm guessing I should add something to the filebeat.yml, but there doesn't seem to be a placeholder for "modules.apache" or similar.

I'm trialling on MacOSX, will be deploying on Ubuntu, but I don't believe this to be a platform-specific question.

**Tags:** configuration, logstash


---

## 1 answers

### Answer by username_0 on 2017-04-08. Score: 3 | Accepted answer

After looking a bit further, I found it in the sample called filebeat.full.yml

So I added this section to the filebeat.yml
Restarted filebeat 

After running at 100% CPU for minute, Kibana is now immediately showing the results. That was easier than I expected.
#==========================  Modules configuration ============================
filebeat.modules:

#------------------------------- Apache2 Module ------------------------------
- module: apache2
  # Access logs
  access:
    #enabled: true

    # Set custom paths for the log files. If left empty,
    # Filebeat will choose the paths depending on your OS.
    var.paths: ["MY-CUSTOM-PATH"]


---

