-
Notifications
You must be signed in to change notification settings - Fork 513
[Box Events] Remove non-ECS fields in ECS namespace #15947
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
base: main
Are you sure you want to change the base?
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
💚 Build Succeeded
|
chrisberkhout
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.
Can't these values be move to actual ECS fields?
For example:
related.location.{lat,lon} --> geo.location.{lat,lon}
| - version: "2.16.0" | ||
| changes: | ||
| - description: | | ||
| Remove non-ECS fields that are collided with ECS namespace. | ||
| Following fields will no longer be available: | ||
| `related.location.lat`, `related.location.lon`, `related.description`, `related.indicator_type`. | ||
| type: breaking-change | ||
| link: https://github.com/elastic/integrations/pull/15947 |
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.
A breaking change should increment the major version number.
Proposed commit message
Checklist
changelog.ymlfile.How to test this PR locally
Related issues