- Notifications
You must be signed in to change notification settings - Fork 519
[Arista NG Firewall] Bugs in Default Ingest Pipeline #6878
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
Conversation
| /test |
🌐 Coverage report
|
| Can you see where it failed? I can see the script exited with error 1, but I don't see any errors above that. |
| In the error post by elasticmachine you can see So you'll need to add that field definition. |
packages/arista_ngfw/data_stream/log/elasticsearch/ingest_pipeline/default.yml Show resolved Hide resolved
| Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
| /test |
| Grrr... can you test again? |
| /test |
packages/arista_ngfw/data_stream/log/elasticsearch/ingest_pipeline/default.yml Outdated Show resolved Hide resolved
| /test |
efd6 left a comment
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.
Thanks
| Package arista_ngfw - 0.1.1 containing this change is available at https://epr.elastic.co/search?package=arista_ngfw |
Type of change
What does this PR do?
Two issues have been identified with the Ingest Pipeline:
event.typewas being set to "denied" where it should have been "allowed"event.typewas getting duplicate entries of "denied"Checklist
changelog.ymlfile.manifest.ymlfile.Author's Checklist
event.typeshould be "allowed"event.typeRelated issues