-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Filebeat][Fortinet Module] fortinet.firewall.addr is not always an IP address, causing ingest errors #25585
Comments
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
There are no sample logs with this situation. I can make this change easily. @fredtj can you provide some sample logs that I can use in the testing to validate the changes?? |
Use these logs for your testing and ignore the previous sample, as that had extra fields added by FortiAnalyzer, which is not supported by this module yet.
|
Also if u want to make a separate issue for the fortiAnalyzer, I'd be happy to work on that with u, either updating the existing filesets or create a new one. |
@legoguy1000 see here: #19315 |
@fredtj PR is ready for review. If you have any comments, let me know. |
Hello,
See error message below:
It seems when Fortigate updates a dynamic address book entry, the resulting log message spits out the object name and not an IP. This causes the above error and the document is not ingested.
I fixed this on my set up by adding the following to the firewall pipeline:
I'm not sure if this is the correct approach, but it does seem to have resolved the issue and those logs are now ingested correctly.
The text was updated successfully, but these errors were encountered: