[
https://issues.apache.org/jira/browse/METRON-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006456#comment-16006456
]
ASF GitHub Bot commented on METRON-941:
---------------------------------------
Github user ctramnitz commented on the issue:
https://github.com/apache/incubator-metron/pull/579
Do you have any examples? The previous concept was to use arbitrary (at
least I couldn't find any reference) field names (i.e. source_address or
destination_address) and then further down these were renamed to "standard"
Metron style (i.e. outputMessage.put("ip_src_addr",
outputMessage.remove("source_address"));). I started to use the "official"
field names (as per vendor documentation), but I still rename the defined field
names to Metron style... did I miss any?
> native PaloAlto parser corrupts message when having a comma in the payload
> --------------------------------------------------------------------------
>
> Key: METRON-941
> URL: https://issues.apache.org/jira/browse/METRON-941
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.4
> Environment: full-dev master
> Reporter: Christian Tramnitz
> Priority: Minor
>
> When a data field contains a comma (i.e. the URL, not too uncommon), the
> split(",") kicks in and the rest of the message if off by few fields due to
> positional definition.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
