Skip to content

Conversation

aleksmaus
Copy link
Contributor

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_address or *_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

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

Related issues

@aleksmaus aleksmaus added enhancement New feature or request Team:Security-Deployment and Devices DEPRECATED Deployment and Devices Security team [elastic/sec-deployment-and-devices] labels Sep 19, 2024
@aleksmaus aleksmaus self-assigned this Sep 19, 2024
@aleksmaus aleksmaus requested a review from a team as a code owner September 19, 2024 21:21
@elasticmachine
Copy link

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

@andrewkroh andrewkroh added the Integration:netflow NetFlow Records label Sep 19, 2024
@elastic-vault-github-plugin-prod

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@aleksmaus aleksmaus requested review from andrewkroh and a team September 19, 2024 21:51
Copy link
Contributor

@taylor-swanson taylor-swanson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to handle observer.ip as well?

@aleksmaus
Copy link
Contributor Author

Do we want to handle observer.ip as well?

I don't know what are the rules. Do we usually add that related.ip?
The original ticket doesn't say anything about this.

@taylor-swanson
Copy link
Contributor

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.

@taylor-swanson
Copy link
Contributor

This is what ECS says about related.ip:

Screenshot 2024-09-23 at 8 37 24 AM

@aleksmaus
Copy link
Contributor Author

Added observer.ip to related.ip

Copy link

@elasticmachine
Copy link

💚 Build Succeeded

History

cc @aleksmaus

@aleksmaus aleksmaus merged commit 2d91393 into elastic:main Sep 23, 2024
5 checks passed
@elastic-vault-github-plugin-prod

Package netflow - 2.19.0 containing this change is available at https://epr.elastic.co/search?package=netflow

harnish-crest-data pushed a commit to chavdaharnish/integrations that referenced this pull request Feb 4, 2025
…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
harnish-crest-data pushed a commit to chavdaharnish/integrations that referenced this pull request Feb 5, 2025
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Integration:netflow NetFlow Records Team:Security-Deployment and Devices DEPRECATED Deployment and Devices Security team [elastic/sec-deployment-and-devices]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

NetFlow Records Integration: Append Network Address Translation IP fields to related.ip
4 participants