Skip to content

Conversation

@taylor-swanson
Copy link
Contributor

@taylor-swanson taylor-swanson commented Mar 11, 2024

Proposed commit message

  • Ensure that the NAT ip and port are removed prior to other processors if they are unset (values of '0.0.0.0' and '0', respectively)
  • Update test files, sample_event, and readme

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.

How to test this PR locally

cd packages/panw elastic-package test 

Related issues

- Ensure that the NAT ip and port are removed prior to other processors if they are unset (values of '0.0.0.0' and '0', respectively) - Update test files, sample_event, and readme
@taylor-swanson taylor-swanson added bug Something isn't working, use only for issues Integration:panw Palo Alto Next-Gen Firewall Team:Security-Deployment and Devices DEPRECATED Deployment and Devices Security team [elastic/sec-deployment-and-devices] labels Mar 11, 2024
@taylor-swanson taylor-swanson self-assigned this Mar 11, 2024
@elasticmachine
Copy link

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

💚 Build Succeeded

cc @taylor-swanson

@taylor-swanson taylor-swanson marked this pull request as ready for review March 11, 2024 19:22
@taylor-swanson taylor-swanson requested a review from a team as a code owner March 11, 2024 19:22
@elasticmachine
Copy link

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

Copy link
Contributor

@jrmolin jrmolin left a comment

Choose a reason for hiding this comment

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

So this was happening too late in the pipeline?

@taylor-swanson
Copy link
Contributor Author

So this was happening too late in the pipeline?

Correct, the remove processors were at the end, but there were some append processors before it that added the nat ip to related.ip.

@taylor-swanson taylor-swanson merged commit 97ac856 into elastic:main Mar 12, 2024
@taylor-swanson taylor-swanson deleted the bugfix/panw-nat-ip branch March 12, 2024 15:05
@elasticmachine
Copy link

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

gizas pushed a commit that referenced this pull request Mar 13, 2024
- Ensure that the NAT ip and port are removed prior to other processors if they are unset (values of '0.0.0.0' and '0', respectively) - Update test files, sample_event, and readme
qcorporation pushed a commit that referenced this pull request Feb 3, 2025
- Ensure that the NAT ip and port are removed prior to other processors if they are unset (values of '0.0.0.0' and '0', respectively) - Update test files, sample_event, and readme
qcorporation pushed a commit that referenced this pull request Feb 4, 2025
- Ensure that the NAT ip and port are removed prior to other processors if they are unset (values of '0.0.0.0' and '0', respectively) - Update test files, sample_event, and readme
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working, use only for issues Integration:panw Palo Alto Next-Gen Firewall Team:Security-Deployment and Devices DEPRECATED Deployment and Devices Security team [elastic/sec-deployment-and-devices]

3 participants