Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cherry-pick #19335 to 7.x: Fix fortinet.firewall.mem value to be interpreted as integer #20542

Merged
merged 1 commit into from
Aug 11, 2020
Merged

Cherry-pick #19335 to 7.x: Fix fortinet.firewall.mem value to be interpreted as integer #20542

merged 1 commit into from
Aug 11, 2020

Commits on Aug 11, 2020

  1. Fix fortinet.firewall.mem value to be interpreted as integer (elastic… 

    …#19335)

Fix fortinet.firewall.mem value to be interpreted as integer. Add convert processor for fortinet.firewall.mem to ingest pipeline.

Closes elastic#19327

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
(cherry picked from commit e7c0b1d)
    @philippkahr @andrewkroh
    philippkahr authored and andrewkroh committed Aug 11, 2020
    Configuration menu
    Copy the full SHA
    8cd7c0c View commit details
    Browse the repository at this point in the history