The SetSecurityUserProcessor auguments ingested documents by adding an user object, where the username field does not conform to the recommended naming convention (name) described in ECS. The purpose of this issue is to faciliate discussion on whether we should rename this field.
PS: there are a few other fields under the user object. They are either confirm to ECS (email, full_name) or have no definition in ECS, i.e. custom fields (metadata, roles etc). Both situations are valid per ECS spec.
The SetSecurityUserProcessor auguments ingested documents by adding an user object, where the
usernamefield does not conform to the recommended naming convention (name) described in ECS. The purpose of this issue is to faciliate discussion on whether we should rename this field.PS: there are a few other fields under the user object. They are either confirm to ECS (
email,full_name) or have no definition in ECS, i.e. custom fields (metadata,rolesetc). Both situations are valid per ECS spec.