Skip to content

user.group should not be a keyword field, but a place where we can nest the group field set #304

@webmat

Description

@webmat

The current definition of the field user.group is problematic, in that it's a place to put a textual group name. This doesn't leave room for other bits of metadata related to a group (the most obvious one being group.id).

The user.group field actually goes against our principle of not reusing the name of a field set (group) as a field with a different meaning (user.group being a string, rather than the nested field set).

This issue came up while working on the right way to represent the various users/groups that went into determining effective rights: elastic/beats#10192, elastic/beats#9963 and elastic/beats#10111.

I would like to suggest we make this change for ECS 1.0.0 GA.

Discuss ;-)

cc @ruflin @MikePaquette @cwurm @andrewkroh

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions