In migrating Beats to ECS for 7.0, we've initially used the ecs-migration.yml file as a place to list all fields that were being aliased or moved for the ECS migration specifically.
Some Beats also appear to have made breaking changes to fields independently of the ECS migration.
As far as I understand, the Breaking changes in 7.0 is generated based on the ecs-migration.yml file, which currently doesn't list all the changes.
The result is that not all of the field breaking changes are listed on this page.
The "breaking changes" page should be updated to include all fields that have a breaking change. See comments below, for non-exhaustive notes of what I observed.
Note that the YAML file could potentially be a very useful file to send customers to, in order to help them perform their migration. So my preference would be that this file is renamed/repurposed to list all changes from 6 to 7, not just the ECS changes.
In migrating Beats to ECS for 7.0, we've initially used the
ecs-migration.ymlfile as a place to list all fields that were being aliased or moved for the ECS migration specifically.Some Beats also appear to have made breaking changes to fields independently of the ECS migration.
As far as I understand, the Breaking changes in 7.0 is generated based on the
ecs-migration.ymlfile, which currently doesn't list all the changes.The result is that not all of the field breaking changes are listed on this page.
The "breaking changes" page should be updated to include all fields that have a breaking change. See comments below, for non-exhaustive notes of what I observed.
Note that the YAML file could potentially be a very useful file to send customers to, in order to help them perform their migration. So my preference would be that this file is renamed/repurposed to list all changes from 6 to 7, not just the ECS changes.