-
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
Cherry-pick #20792 to 7.x: [ECS] Update ecs to 1.6.0 #20863
Conversation
Pinging @elastic/siem (Team:SIEM) |
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
* Update ecs to 1.6.0 * Update fields.ecs.yml and re generate fields files * Remove filebeat duplicated cloud.project.id * Remove filebeat duplicated log.file.path * Remove repeated cloud.project.id from remaining beats * Remove duplicated x509.* fields from metricbeat * Remove duplicated x509.* fields in packetbeat * Remove duplicated field log.file.path from winlogbeat * Add missing exports tests and better error message * Run make fmt (cherry picked from commit ef457ea)
ff7038d
to
0381bf1
Compare
Cherry-pick of PR #20792 to 7.x branch. Original message:
What does this PR do?
Updates ecs to 1.6.0.
Why is it important?
So we can update Beats to ship data using 1.6 fields.
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 documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Relates to #19472