2.3.260 Issue to parse fortinet logs with filebeat #11453
Replies: 4 comments 6 replies
-
Try putting Filebeat into debug and see if there are any clues in the log? Put the below in your
|
Beta Was this translation helpful? Give feedback.
-
Hello there! I have a little different of a setup, but I was able to get Fortinet logging to work with my 2.3 deployment. My setup is two forward nodes, and a managersearch node. This is what I did to get it to work for me. I don't know if this will specifically help, but maybe we can compare/contrast and troubleshoot from there. I think the main differences are that I'm sending logs directly to the Managersearch, and not to sensor nodes. I also applied the config changes to the specific minion pillar and not to global. Maybe there is an issue between the sensor/forward nodes and the search/manager nodes that gets the filebeat to logstash wrong? Within /opt/so/saltstack/local/pillar/minions/$managersearch.sls config I added: Then I ran: sudo so-allow -> s -> With my network, I have VLANs, so I have to use the gateway IP for how my managersearch node sees each Fortigate. Within the FortiGate: config log syslogd setting Then, back to the Managersearch node. I ran the following commands: Then I edited the managersearch config again (/opt/so/saltstack/local/pillar/minions/$managersearch.sls) Lastly, I ran: sudo salt-call state.apply firewall And I began getting parsed Fortinet logs. I am running 6.4.14 as well. I don't know if it is parsing all of the logs, but I am getting plenty of them to work with. |
Beta Was this translation helpful? Give feedback.
-
Also check the following:
See if there are any clues in the above. |
Beta Was this translation helpful? Give feedback.
-
Change the below to you sensor's minion pillar file in
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have a distributed SO deployment running, and I cannot find what I did wrong so my Fortinet firewall logs are not parsed by the filebeat module.
The architecture
1 manager/search node
2 search node
1 forwarder
Version: 2.3.260 (updated from 2.3.40)
(In this question FW_IP_address mask the real entry)
The firewall (fortigate 6.4.14) is set to sent its logs directly to the udp 9004 manager port
I can see the flow is coming with tcpdump (see below)
What I did:
In /opt/so/saltstack/local/pillar/global.sls
Same in manager.sls, and both search nodes minions sls files without the "INPUT" part.
I created a fortigate hostgroup and portgoup then add the firewall IP address
That I can see:
The filebeat docker port is open and listening
And
And these logs:
I try to apply the documentation and aswers from other issues, for example:
#9705
Thanks for any help or clue :)
Beta Was this translation helpful? Give feedback.
All reactions