[netflow]: Append all ip addresses found to the related.ip field. - #11193
Conversation
|
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
🚀 Benchmarks reportTo see the full report comment with |
taylor-swanson
left a comment
There was a problem hiding this comment.
Do we want to handle observer.ip as well?
I don't know what are the rules. Do we usually add that |
|
I poked around other integrations. While we're not great at setting related fields, I am seeing other integrations adding observer fields to the related fields, so we should do the same here. If you don't want to mess with the painless script, you could add an append processor for observer.ip instead. |
|
Added observer.ip to related.ip |
|
💚 Build Succeeded
History
cc @aleksmaus |
|
Package netflow - 2.19.0 containing this change is available at https://epr.elastic.co/search?package=netflow |
…astic#11193) * [netflow]: Append all ip addresses found to related.ip field. * Update changelog PR number * Address code review * Add observer.ip to related.ip
…astic#11193) * [netflow]: Append all ip addresses found to related.ip field. * Update changelog PR number * Address code review * Add observer.ip to related.ip





Proposed commit message
Append all ip addresses found to the related.ip field.
I was not sure if the original issue meant specific fields, if yes then ipv6 was not included in the list.
Anyways, in the first cut appending all the fields that end with
*_ipv4_addressor*_ipv6_address.Can redo if the list of the fields limited to just: netflow.post_nat_destination_ipv4_address , netflow.post_nat_source_ipv4_address, netflow.post_nat_destination_ipv6_address , netflow.post_nat_source_ipv6_address.
Let me know.
Checklist
changelog.ymlfile.Related issues