# Parsing fortigate logs with filebeat modules

**URL:** <https://discuss.elastic.co/t/parsing-fortigate-logs-with-filebeat-modules/306391>\
**Category:** Beats\
**Tags:** beats-module, filebeat\
**Created:** [June 4, 2022, 8:54pm UTC](https://discuss.elastic.co/t/parsing-fortigate-logs-with-filebeat-modules/306391 "2022-06-04T20:54:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![frank\_rib](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frank_rib/32/104372_2.png) [@frank\_rib](https://discuss.elastic.co/u/frank_rib)\
**Post date:** [June 4, 2022, 8:54pm UTC](https://discuss.elastic.co/t/parsing-fortigate-logs-with-filebeat-modules/306391/1 "2022-06-04T20:54:35Z")

</div>

Hello,  
I have never used filebeat for parsing the fortigate logs. I have consulted several pages on the internet about this.  
I concluded that the best approach is to install Filebeat at the logstash server, after activating the fortigate filebeat module and listening on a port (For example 9001). We shall configure fortigate to send logs to the logstash server address via the configured port.  
My question :  
Are the steps I mentioned correct?

Thanks,

---

<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:** [July 2, 2022, 10:55pm UTC](https://discuss.elastic.co/t/parsing-fortigate-logs-with-filebeat-modules/306391/2 "2022-07-02T22:55:03Z")

</div>

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