-
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
adding observer.zone/interface following ECS 1.5.0 #18600
Conversation
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? |
Pinging @elastic/siem (Team:SIEM) |
jenkins, run tests |
❕ Build Aborted
Expand to view the summary
Build stats
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
These fields were added in #18525 so I'm closing this. |
What does this PR do?
Added observer.[e|in]gress.zone and observer.[e|in]gress.interface.name
Why is it important?
observer.zone is defined on ECS 1.5.0
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Use cases
The fix adds observer elements and doesn't remove anything.
BTW panw.panos.source.zone, panw.panos.destination.zone, panw.panos.source.interface and panw.panos.destination.interface can be now removed.