-
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][Cisco ASA] log enhancement and performance #20831
Conversation
- Fixed some ECS issues - added anchors on grok patterns for performance - added messages: ------------------------- 434004 434002 713905 750002 750003 110002 419002 602304 602303 713120 713202 713901 713904 713906 713905 ------------------------- - with the messages pattern added also this commit add four new event action types in the script that mapped event actions to the event.kind/category/type - added set processor for adding outcome, action and protocol if necessary for the new messages
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
|
Test | Results |
---|---|
Failed | 1 |
Passed | 2444 |
Skipped | 263 |
Total | 2708 |
Genuine test errors
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
Build&Test / x-pack/filebeat-build / test_fileset_file_203_juniper – x-pack.filebeat.tests.system.test_xpack_modules.XPackTest
Pinging @elastic/siem (Team:SIEM) |
fix parsing error and add enhancements
fix 602303
@pcosic Would you be able to generate some new test files to see how it would impact the test files? Inside the x-pack filebeat folder run: |
@P1llus Sorry that I didn't do this earlier. I committed all the changes and here is the Output of the test:
Is there anything else needed? |
x-pack/filebeat/module/cisco/shared/ingest/asa-ftd-pipeline.yml
Outdated
Show resolved
Hide resolved
Hi! We're labeling this issue as |
+1 |
@pcosic are you able to merge with master? There is a conflict with x-pack/filebeat/module/cisco/fields.go |
run tests |
commit after running tests.
I just had to write a comment to trigger the CI, no worries :) |
Can someone run a test again? |
jenkins run tests |
It looks like I failed because of 106014, originally I did not want to change this message id with my PR. |
Hey @pcosic , Sorry for the delay, you are indeed correct that not all issues with the test logs are related to your PR. There might be some delays with the answers, but let me also tag in @jamiehynds to see if he can keep an overview on this PR and maybe share some details. |
This fixing finally 106014. We have, afaik, two options. Use IPORHOST to not match '(type' or using '(?<destination.address>[^ (]*)' so we only dispense on space or '(' for the case destination.address is weird. NOTSPACE is not work in this case.
sorry this was my mistake. I think 106014 shouldn't be a problem anymore, and the PR would pass the tests with the last commit. Maybe run test again 👍 ? |
jenkins run tests |
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
Jenkins run tests |
I have changed what you @adriansr requested at the Cr and it would be nice to get your approval |
Hi! We're labeling this issue as |
hello @pcosic ! Can you please update the branch with master so I can run the tests again? Thanks! |
you can start the test @marc-gr if you want. |
jenkins run tests |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
I pulled these commits into a new PR, resolved the merge conflicts, and added a changelog entry. #24744 |
What does this PR do?
This PR resolve some reported issues with ECS, and is adding new message pattern for ASA logs
Overview of the Changes:
fix parsing error not extracting event.outcome and network.transport from 106015
all other processors associated with the new message id's have been updated and extended
further additional fields were derived from the logs
changed event.outcome in script processor to ECS
adding anchors to grok patterns with no conditional and to grok processors that using more than one pattern
adding new event.action for user creation/deletion or bypass events
fix 106014
Why is it important?
We think that these are one of the most used message types in Cisco ASA logs.
adding the anchors increases the throughput/performance. It is described in more detail in this blog article (https://www.elastic.co/blog/do-you-grok-grok)
Wee need more event.actions for specific logs/events
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs