@ruflin This one will annoy you as well. Non-breaking change, because since the OSQuery module reads "userland" data (directly related to their query), I'm copying out a few bit of info without renaming anything.

As discussed in the other PR, let's not do this and rely on aliases.

@ruflin Ready for a quick review. No breaking changes here. Test failures unrelated (heartbeat and libbeat)

@webmat See other PR for the comments related to alias. We should go with alias instead of copying.

@ruflin Are you saying we should move the data to the ECS field name, and put in place an alias inside the user's query result objects towards the ECS name?

@tsg How were these events generated, by the way? The /test/ log examples don't look like answers to ad hoc queries. It looks more like the result of some structured sets of queries. Are the following fields expected to be present most of the time? .host_identifier, .decorations.host_uuid and .decorations.username

@webmat I'm suggestion we do here the same as for all other modules.

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b ecs-osquery-fb upstream/ecs-osquery-fb
git merge upstream/master
git push upstream ecs-osquery-fb