# Filebeat sending logs issue

**URL:** <https://discuss.elastic.co/t/filebeat-sending-logs-issue/234507>\
**Category:** Beats\
**Tags:** beats-module, filebeat\
**Created:** [May 27, 2020, 9:51am UTC](https://discuss.elastic.co/t/filebeat-sending-logs-issue/234507 "2020-05-27T09:51:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![PierreR](https://avatars.discourse-cdn.com/v4/letter/p/b5a626/32.png) [@PierreR](https://discuss.elastic.co/u/PierreR)\
**Post date:** [May 27, 2020, 9:51am UTC](https://discuss.elastic.co/t/filebeat-sending-logs-issue/234507/1 "2020-05-27T09:51:51Z")

</div>

Hello everyone,

I have a problem with the Filebeat inputs. I installed and configured Filebeat on a **CentOS 7** with **Prelude SIEM** installed. I am using Filebeat to transmit the logs from **Prelude to ELK**. For the moment the "system" logs (module "system" activated) are sent correctly to my remote ELK server, but this is not the case for the **"prelude-xml.log**" and **"prelude.log"** log files.

My file "filebeat.yml" seems to be correctly configured with the correct paths to the log file:

```auto
    filebeat.inputs:

    - type: log
        - /var/log/prelude.log
        - /var/log/prelude-xml.log

```

The "system" module is well deactivated and the "prelude-xml.log" file seems to be loaded by Filebeat:

```auto
    mai 27 11:45:43 localhost.localdomain filebeat[3330]: 2020-05-27T11:45:43.325+0200 WARN beater/filebeat.go:368 Filebeat is unable to load the Ingest Node pipelines for the configured modu...
    mai 27 11:45:43 localhost.localdomain filebeat[3330]: 2020-05-27T11:45:43.325+0200 INFO crawler/crawler.go:72 Loading Inputs: 1
    mai 27 11:45:43 localhost.localdomain filebeat[3330]: 2020-05-27T11:45:43.325+0200 INFO [monitoring] log/log.go:118 Starting metrics logging every 30s
    mai 27 11:45:43 localhost.localdomain filebeat[3330]: 2020-05-27T11:45:43.329+0200 INFO log/input.go:152 Configured paths: [/var/log/prelude.log /var/log/prelude-xml.log]
    mai 27 11:45:43 localhost.localdomain filebeat[3330]: 2020-05-27T11:45:43.329+0200 INFO input/input.go:114 Starting input of type: log; ID: 15332088532770242788
    mai 27 11:45:43 localhost.localdomain filebeat[3330]: 2020-05-27T11:45:43.329+0200 INFO crawler/crawler.go:106 Loading and starting Inputs completed. Enabled inputs: 1
    mai 27 11:45:43 localhost.localdomain filebeat[3330]: 2020-05-27T11:45:43.330+0200 INFO cfgfile/reload.go:171 Config reloader started
    mai 27 11:45:43 localhost.localdomain filebeat[3330]: 2020-05-27T11:45:43.331+0200 INFO cfgfile/reload.go:226 Loading of config files completed.
    mai 27 11:45:43 localhost.localdomain filebeat[3330]: 2020-05-27T11:45:43.437+0200 INFO log/harvester.go:251 Harvester started for file: /var/log/prelude-xml.log
    mai 27 11:45:43 localhost.localdomain filebeat[3330]: 2020-05-27T11:45:43.438+0200 INFO log/harvester.go:251 Harvester started for file: /var/log/prelude.log

```

I have done a lot of tests with differents configurations and despite some research on forums, I did not find a solution.

I do not think I understood very well how Filebeat works, my log file being in "XML" format, do I need an **XML module** for example?

Anyone has an idea 🙂 ? Thank you!

Pierre

---

<div class="post-metadata">

**Author:** ![MarianaD](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marianad/32/42687_2.png) [@MarianaD](https://discuss.elastic.co/u/MarianaD)\
**Post date:** [May 27, 2020, 10:08am UTC](https://discuss.elastic.co/t/filebeat-sending-logs-issue/234507/2 "2020-05-27T10:08:43Z")

</div>

hi @PierreR,

Not sure you can do this with only Filebeat.  
You could use multiline in Filebeat to group all the lines from the request and response into one event.

```auto
filebeat.prospectors:
  - paths: ['/var/log/prelude-xml.log']
    multiline.pattern: ^<{the start of your line}>
    multiline.negate: true
    multiline.match: after

```

Then in either [Logstash](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html) or [Ingest Node](https://www.elastic.co/guide/en/elasticsearch/reference/current/grok-processor.html), use grok to parse the request, response, and text about the request into separate fields.

Apply then the [xml](https://www.elastic.co/guide/en/logstash/current/plugins-filters-xml.html) filter to parse those messages.

---

<div class="post-metadata">

**Author:** ![PierreR](https://avatars.discourse-cdn.com/v4/letter/p/b5a626/32.png) [@PierreR](https://discuss.elastic.co/u/PierreR)\
**Post date:** [May 27, 2020, 12:04pm UTC](https://discuss.elastic.co/t/filebeat-sending-logs-issue/234507/3 "2020-05-27T12:04:39Z")

</div>

Thanks for your help @MarianaD 😃 !

I will test with Filebeat Prospectors and I will let you know if it works.

Pierre

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 24, 2020, 12:04pm UTC](https://discuss.elastic.co/t/filebeat-sending-logs-issue/234507/4 "2020-06-24T12:04:45Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.