# Difficulty in enabling Netflow in Filebeat

**URL:** <https://discuss.elastic.co/t/difficulty-in-enabling-netflow-in-filebeat/205723>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [October 29, 2019, 4:53pm UTC](https://discuss.elastic.co/t/difficulty-in-enabling-netflow-in-filebeat/205723 "2019-10-29T16:53:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thebeaoliveira](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thebeaoliveira/32/53314_2.png) [@thebeaoliveira](https://discuss.elastic.co/u/thebeaoliveira)\
**Post date:** [October 29, 2019, 4:53pm UTC](https://discuss.elastic.co/t/difficulty-in-enabling-netflow-in-filebeat/205723/1 "2019-10-29T16:53:06Z")

</div>

Hello!

I am starting to test SIEM (v7.4.1) and have come across a bit of trouble enabling Netflow in Filebeat.

I need to do a configuration in Linux (CentOS 7) and Windows Server environments.

I can get the Filebeat service up, but it doesn't send any logs to Elasticsearch.

I already tested the config and it returns **OK**.

I suppose that might be the way I'm addressing the logs, in this case the paths I'm using are these:

Windows:

```auto
- C:\Windows\System32\winevt\Logs\Security
- C:\Windows\System32\winevt\Logs\Application

```

Linux

```auto
- /var/log/*.log
- /var/log/messages

```

Can you tell me if you are right?

---

<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:** [November 26, 2019, 4:53pm UTC](https://discuss.elastic.co/t/difficulty-in-enabling-netflow-in-filebeat/205723/2 "2019-11-26T16:53:08Z")

</div>

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