Group fields
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
The group fields are meant to represent groups that are relevant to the event.
| Field | Description | Level |
|---|---|---|
| group.domain | Name of the directory the group is a member of. For example, an LDAP or Active Directory domain name. type: keyword |
extended |
| group.id | Unique identifier for the group on the system/platform. type: keyword |
extended |
| group.name | Name of the group. type: keyword |
extended |
The group fields are expected to be nested at:
process.attested_groupsprocess.groupprocess.real_groupprocess.saved_groupprocess.supplemental_groupsuser.group
Note also that the group fields may be used directly at the root of the events.