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

fortinet.firewall.mem string value #19327

Closed
kristenungdom opened this issue Jun 21, 2020 · 3 comments · Fixed by #19335
Closed

fortinet.firewall.mem string value #19327

kristenungdom opened this issue Jun 21, 2020 · 3 comments · Fixed by #19335

Comments

@kristenungdom
Copy link

filebeat 7.8 mapps the performance field fortinet.firewall.mem as string rather than Number field in the Fortinet Module
@cbuescher cbuescher transferred this issue from elastic/elasticsearch Jun 23, 2020
@cbuescher
Copy link
Member

Moving to the beats repo.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 23, 2020
@philippkahr philippkahr mentioned this issue Jun 23, 2020
Merged
3 tasks
@philippkahr
Copy link
Contributor

I just submitted a PR #19335 for this issue

@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 24, 2020
andrewkroh added a commit that referenced this issue Aug 11, 2020
@philippkahr @andrewkroh
Fix fortinet.firewall.mem value to be interpreted as integer (#19335)
e7c0b1d 
Fix fortinet.firewall.mem value to be interpreted as integer. Add convert processor for fortinet.firewall.mem to ingest pipeline.

Closes #19327

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
andrewkroh pushed a commit to andrewkroh/beats that referenced this issue Aug 11, 2020
@philippkahr @andrewkroh
Fix fortinet.firewall.mem value to be interpreted as integer (elastic…
8cd7c0c 
…#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)
@andrewkroh andrewkroh mentioned this issue Aug 11, 2020
Merged
3 tasks
andrewkroh added a commit that referenced this issue Aug 11, 2020
@andrewkroh @philippkahr
Fix fortinet.firewall.mem value to be interpreted as integer (#19335) (…
9a3bef6 
…#20542)

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

Closes #19327

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
(cherry picked from commit e7c0b1d)

Co-authored-by: Philipp Kahr <philipp.kahr@icloud.com>
melchiormoulin pushed a commit to melchiormoulin/beats that referenced this issue Oct 14, 2020
@philippkahr @andrewkroh @melchiormoulin
Fix fortinet.firewall.mem value to be interpreted as integer (elastic…
c4df757 
…#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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix fortinet.firewall.mem value to be interpreted as integer
5 participants
@andresrc @kristenungdom @cbuescher @philippkahr @elasticmachine