-
Notifications
You must be signed in to change notification settings - Fork 497
[SOPHOS UTM] Add GeopIP conditions #15130
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.
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
[SOPHOS UTM] Add GeopIP conditions #15130
Conversation
🚀 Benchmarks reportTo see the full report comment with |
Pinging @elastic/integration-experience (Team:Integration-Experience) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look OK.
Question: are you not seeing these type of behaviour within any of the other geoip: process.
I see similar processing within
- utm/../dhcp.yml
- utm/../dns.yml
- xg/../default.yml
I observed the issue so far just on the http & packet filter, but you're right, it's the same on the other geoip processors. I added that as well |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
💚 Build Succeeded
History
|
|
Package sophos - 3.15.2 containing this change is available at https://epr.elastic.co/package/sophos/3.15.2/ |
Prevent pipeline errors if source/destionation .ip is a empty string