filebeat default home path ?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

filebeat default home path ?

Landry Breuil-5
Hi,

struggling a bit with filebeat, i think the current rc script lacks
-path.home ${PREFIX}/share/filebeat as it seems that's where it looks
for modules.

if i dont specify it, with the default config and the default daemon
args:

[11:41] c64:~/mystuff/sysutils/beats/ $doas filebeat -path.config /etc/filebeat  -e
...
2019-11-10T11:41:59.383+0100    ERROR   fileset/modules.go:125  Not loading modules. Module directory not found: /home/landry/mystuff/sysutils/beats/module

if i specify it, seems much better.

[11:42] c64:~/mystuff/sysutils/beats/ $doas filebeat -path.config /etc/filebeat -path.home /usr/local/share/filebeat -e
2019-11-10T11:42:33.196+0100    INFO    instance/beat.go:607    Home path: [/usr/local/share/filebeat] Config path: [/etc/filebeat] Data path: [/usr/local/share/filebeat/data] Logs path: [/usr/local/share/filebeat/logs]

so i wonder if daemon_flags should be amended in
sysutils/beats/filebeat/pkg/filebeat.rc ?

according to
https://www.elastic.co/guide/en/beats/filebeat/master/configuration-path.html
maybe logs & data paths should be specified so that this thing works 'better'
out of the box ? or i'm missing something ? does this have smth to do with the
BEATS_MODULES var, which is true only for filebeat and not the other beats ?

Landry

Reply | Threaded
Open this post in threaded view
|

Re: filebeat default home path ?

Landry Breuil-5
On Sun, Nov 10, 2019 at 11:45:58AM +0100, Landry Breuil wrote:

> Hi,
>
> struggling a bit with filebeat, i think the current rc script lacks
> -path.home ${PREFIX}/share/filebeat as it seems that's where it looks
> for modules.
>
> if i dont specify it, with the default config and the default daemon
> args:
>
> [11:41] c64:~/mystuff/sysutils/beats/ $doas filebeat -path.config /etc/filebeat  -e
> ...
> 2019-11-10T11:41:59.383+0100    ERROR   fileset/modules.go:125  Not loading modules. Module directory not found: /home/landry/mystuff/sysutils/beats/module
>
> if i specify it, seems much better.
>
> [11:42] c64:~/mystuff/sysutils/beats/ $doas filebeat -path.config /etc/filebeat -path.home /usr/local/share/filebeat -  
> 2019-11-10T11:42:33.196+0100    INFO    instance/beat.go:607    Home path: [/usr/local/share/filebeat] Config path: [/etc/filebeat] Data path: [/usr/local/share/filebeat/data] Logs path: [/usr/local/share/filebeat/logs]
>
> so i wonder if daemon_flags should be amended in
> sysutils/beats/filebeat/pkg/filebeat.rc ?
>
> according to
> https://www.elastic.co/guide/en/beats/filebeat/master/configuration-path.html
> maybe logs & data paths should be specified so that this thing works 'better'
> out of the box ? or i'm missing something ? does this have smth to do with the
> BEATS_MODULES var, which is true only for filebeat and not the other beats ?
here's a diff that fixes path.home, and while at it installs the default
provided sample dashboards. played a bit with them on a 6.6 kibana
install (not current, i know) and i had to use the
libbeat/scripts/unpack_dashboards.py script provided in beats source to
massage them, but once installed 'filebeat/metricbeat setup' managed to
push the dashboards to kibana and i finally got some shiny graphs from
my nginx/system logs.

Landry

beats-dashboards.diff (11K) Download Attachment