-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[filebeat][panw] Improve panos fileset url parsing #22481
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
6d8957f
to
2814985
Compare
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
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.
Nice.
x-pack/filebeat/module/panw/panos/test/pan_inc_threat.log-expected.json
Outdated
Show resolved
Hide resolved
x-pack/filebeat/module/panw/panos/test/pan_inc_threat.log-expected.json
Outdated
Show resolved
Hide resolved
x-pack/filebeat/module/panw/panos/test/pan_inc_threat.log-expected.json
Outdated
Show resolved
Hide resolved
d126d80
to
96f7597
Compare
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.
Looks great. Sorry for not seeing the filename stuff in the first review.
* Improve panos url parsing * Do not parse url details when not needed * Parse url based on threat subtype (cherry picked from commit bb973c4)
What does this PR do?
Parse panos url field to extract useful ecs fields.
Why is it important?
To improve ECS support in our modules.
Checklist
- [ ] My code follows the style guidelines of this project- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentationCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.